Skip to content

AROSLSRE-687: propagate HCP Azure resource ID annotation to control plane namespace#8312

Open
ashishmax31 wants to merge 1 commit into
openshift:mainfrom
ashishmax31:AROSLSRE-687
Open

AROSLSRE-687: propagate HCP Azure resource ID annotation to control plane namespace#8312
ashishmax31 wants to merge 1 commit into
openshift:mainfrom
ashishmax31:AROSLSRE-687

Conversation

@ashishmax31

@ashishmax31 ashishmax31 commented Apr 23, 2026

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:

Add a new annotation constant HCPAzureResourceIDAnnotation that carries
the Azure resource ID set by Cluster Service on the HostedCluster CR.
The hostedcluster controller now propagates this annotation to the
hosted control plane namespace for Azure platform clusters.

Fixes
https://redhat.atlassian.net/browse/AROSLSRE-687

Special notes for your reviewer:

Checklist:

  • Subject and description added to both, commit and PR.
  • [x ] Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

Summary by CodeRabbit

  • New Features

    • Azure HostedClusters now propagate an Azure resource ID annotation into their hosted control plane namespace for Azure-based clusters; the annotation is added when present and removed when absent, preserving other namespace annotations.
  • Tests

    • Added unit tests covering propagation, removal, non-Azure behavior, and preservation of existing namespace annotations.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@coderabbitai

coderabbitai Bot commented Apr 23, 2026

Copy link
Copy Markdown
Contributor

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

Adds the exported constant HCPAzureResourceIDAnnotation with value "azure.microsoft.com/hcp-cluster-azure-resource-id". The HostedCluster controller reconciliation propagates that annotation from an Azure-platform HostedCluster CR to the hosted control plane Namespace: it initializes namespace.Annotations if nil, writes the annotation value when present on the HostedCluster, and removes the annotation from the Namespace when the HostedCluster no longer has it. Non-Azure platforms are not affected; other Namespace annotations are preserved.

Sequence Diagram(s)

sequenceDiagram
  participant HC as HostedCluster CR
  participant Ctrl as HostedCluster Controller
  participant API as Kubernetes API (ControlPlane Namespace)

  HC->>Ctrl: Reconcile event / Read HostedCluster
  Ctrl->>Ctrl: Check platform == Azure?
  alt Azure platform
    alt annotation present on HC
      Ctrl->>API: GET ControlPlane Namespace
      API-->>Ctrl: Namespace object
      Ctrl->>Ctrl: Ensure namespace.Annotations initialized
      Ctrl->>API: PATCH/UPDATE Namespace with HCPAzureResourceIDAnnotation
      API-->>Ctrl: 200 OK
    else annotation absent on HC
      Ctrl->>API: GET ControlPlane Namespace
      API-->>Ctrl: Namespace object
      Ctrl->>Ctrl: Remove HCPAzureResourceIDAnnotation from Namespace.Annotations (if present)
      Ctrl->>API: PATCH/UPDATE Namespace
      API-->>Ctrl: 200 OK
    end
  else Non-Azure platform
    Ctrl-->>API: No annotation written or removed
  end
Loading
🚥 Pre-merge checks | ✅ 10 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 20.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Test Structure And Quality ⚠️ Warning Test uses NewWithT instead of NewGomegaWithT (inconsistent with 18 existing tests), lacks meaningful assertion failure messages without explanatory strings. Use NewGomegaWithT(t) for consistency; add meaningful failure messages to assertions like "failed to propagate Azure resource ID annotation".
✅ Passed checks (10 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: propagating an Azure resource ID annotation to the control plane namespace, which aligns with all modified files.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed All new test names in TestPropagateAzureResourceIDAnnotation are static strings without dynamic content, timestamps, UUIDs, or generated identifiers. Test titles are descriptive and deterministic.
Microshift Test Compatibility ✅ Passed Added test (TestPropagateAzureResourceIDAnnotation) is a standard Go unit test, not a Ginkgo e2e test. The custom check only applies to Ginkgo e2e tests, which are not present in this PR.
Single Node Openshift (Sno) Test Compatibility ✅ Passed No Ginkgo e2e tests were added. The PR only adds a standard Go unit test (TestPropagateAzureResourceIDAnnotation) using testing.T, which is outside the scope of this SNO compatibility check.
Topology-Aware Scheduling Compatibility ✅ Passed PR only adds annotation constant and propagates Azure resource ID metadata to namespace; no scheduling constraints (affinity, replicas, nodeSelector, etc.) are introduced.
Ote Binary Stdout Contract ✅ Passed PR is for HyperShift operator codebase (API types, controller, and unit tests), not an OTE binary. Check is not applicable to non-OTE projects.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed No Ginkgo e2e tests added. PR contains only standard Go unit tests in hostedcluster_controller_test.go with no IPv4 or connectivity assumptions.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.


Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot added area/api Indicates the PR includes changes for the API area/hypershift-operator Indicates the PR includes changes for the hypershift operator and API - outside an OCP release and removed do-not-merge/needs-area labels Apr 23, 2026
@openshift-ci openshift-ci Bot requested review from devguyio and jparrill April 23, 2026 06:54

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@hypershift-operator/controllers/hostedcluster/hostedcluster_controller_test.go`:
- Around line 6583-6590: The test currently duplicates the Azure resourceID
annotation propagation logic inline; instead invoke the real reconciliation path
(call HostedClusterReconciler.Reconcile or the production helper used by the
controller) using the fake client with the test's HostedCluster (hcluster) and
Namespace (ns) fixtures, then fetch the Namespace from the fake client and
assert that ns.Annotations[hyperv1.HCPAzureResourceIDAnnotation] matches the
HostedCluster annotation; update the test to remove the inline propagation block
and reference HostedClusterReconciler.Reconcile (or the controller helper
function) and the hcluster/ns fixtures so the assertion verifies controller
behavior end-to-end.

In `@hypershift-operator/controllers/hostedcluster/hostedcluster_controller.go`:
- Around line 1413-1421: The reconcile currently only copies
hyperv1.HCPAzureResourceIDAnnotation from the HostedCluster to the
controlPlaneNamespace when present, but never deletes it when the source
annotation is removed; update the logic in the reconcile block handling
hcluster.Spec.Platform == hyperv1.AzurePlatform (around the
controlPlaneNamespace update) to check for the annotation on the HostedCluster
and if missing remove hyperv1.HCPAzureResourceIDAnnotation from
controlPlaneNamespace (ensure controlPlaneNamespace.Annotations is non-nil
before modifying), then persist the change (e.g., via the existing client
update/patch call used for controlPlaneNamespace) so stale values are cleared.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: a1bf189c-2644-4dbd-8566-929d11783745

📥 Commits

Reviewing files that changed from the base of the PR and between 6daa9ce and 621ee27.

⛔ Files ignored due to path filters (1)
  • vendor/github.com/openshift/hypershift/api/hypershift/v1beta1/hostedcluster_types.go is excluded by !vendor/**, !**/vendor/**
📒 Files selected for processing (3)
  • api/hypershift/v1beta1/hostedcluster_types.go
  • hypershift-operator/controllers/hostedcluster/hostedcluster_controller.go
  • hypershift-operator/controllers/hostedcluster/hostedcluster_controller_test.go

Comment thread hypershift-operator/controllers/hostedcluster/hostedcluster_controller_test.go Outdated
Comment thread hypershift-operator/controllers/hostedcluster/hostedcluster_controller.go Outdated
@codecov

codecov Bot commented Apr 23, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 41.80%. Comparing base (ee9099c) to head (651fed3).
⚠️ Report is 12 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #8312      +/-   ##
==========================================
+ Coverage   41.75%   41.80%   +0.05%     
==========================================
  Files         758      759       +1     
  Lines       93981    94049      +68     
==========================================
+ Hits        39240    39316      +76     
+ Misses      51988    51983       -5     
+ Partials     2753     2750       -3     
Files with missing lines Coverage Δ
...trollers/hostedcluster/hostedcluster_controller.go 46.04% <100.00%> (+0.15%) ⬆️

... and 5 files with indirect coverage changes

Flag Coverage Δ
cmd-support 35.11% <ø> (+0.09%) ⬆️
cpo-hostedcontrolplane 44.10% <ø> (ø)
cpo-other 43.45% <ø> (ø)
hypershift-operator 51.90% <100.00%> (+0.07%) ⬆️
other 31.56% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@JoelSpeed

Copy link
Copy Markdown
Contributor

/approve

For API

@ashishmax31 ashishmax31 marked this pull request as draft April 23, 2026 11:59
@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 23, 2026
@ashishmax31 ashishmax31 force-pushed the AROSLSRE-687 branch 2 times, most recently from e5be0cf to 4088e5f Compare April 27, 2026 08:28
@jparrill

jparrill commented May 4, 2026

Copy link
Copy Markdown
Contributor

/retitle AROSLSRE-687: propagate HCP Azure resource ID annotation to control plane namespace

@openshift-ci openshift-ci Bot changed the title feat(azure): propagate HCP Azure resource ID annotation to control plane namespace AROSLSRE-687: propagate HCP Azure resource ID annotation to control plane namespace May 4, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 4, 2026
@openshift-ci-robot

openshift-ci-robot commented May 4, 2026

Copy link
Copy Markdown

@ashishmax31: This pull request references AROSLSRE-687 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

What this PR does / why we need it:

Add a new annotation constant HCPAzureResourceIDAnnotation that carries
the Azure resource ID set by Cluster Service on the HostedCluster CR.
The hostedcluster controller now propagates this annotation to the
hosted control plane namespace for Azure platform clusters.

Fixes
https://redhat.atlassian.net/browse/AROSLSRE-687

Special notes for your reviewer:

Checklist:

  • Subject and description added to both, commit and PR.
  • [x ] Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

Summary by CodeRabbit

  • New Features

  • Azure HostedClusters now propagate an Azure resource ID annotation into their hosted control plane namespace for Azure-based clusters, improving resource tracking and identification.

  • Tests

  • Added unit tests covering propagation, removal, non-Azure behavior, and preservation of other namespace annotations.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@jparrill jparrill left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dropped a comment. Thanks!

@jparrill

jparrill commented May 4, 2026

Copy link
Copy Markdown
Contributor

/approve

@jparrill

jparrill commented May 4, 2026

Copy link
Copy Markdown
Contributor

You will need to force push in order to retest the env test for KAS.

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 4, 2026
@ashishmax31 ashishmax31 marked this pull request as ready for review May 21, 2026 06:44
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 21, 2026
@openshift-ci openshift-ci Bot requested review from csrwng and enxebre May 21, 2026 06:45

@jparrill jparrill left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dropped some comments. Thanks

Comment thread hypershift-operator/controllers/hostedcluster/hostedcluster_controller.go Outdated
Comment thread hypershift-operator/controllers/hostedcluster/hostedcluster_controller_test.go Outdated
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aks-4-22
/test e2e-aws-4-22
/test e2e-aks
/test e2e-aws
/test e2e-aws-upgrade-hypershift-operator
/test e2e-azure-v2-self-managed
/test e2e-kubevirt-aws-ovn-reduced
/test e2e-v2-aws
/test e2e-v2-gke

@openshift-ci

openshift-ci Bot commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ashishmax31, bryan-cox, JoelSpeed, jparrill

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@hypershift-jira-solve-ci

Copy link
Copy Markdown

AI Test Failure Analysis

Job: pull-ci-openshift-hypershift-main-e2e-aks | Build: 2066501927281102848 | Cost: $3.3587292500000006 | Failed step: hypershift-azure-run-e2e

View full analysis report


Generated by hypershift-analyze-e2e-failure post-step using Claude claude-opus-4-6

@ashishmax31

Copy link
Copy Markdown
Contributor Author

/retest-required

@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Jun 16, 2026
@ashishmax31

Copy link
Copy Markdown
Contributor Author

/retest-required

1 similar comment
@ashishmax31

Copy link
Copy Markdown
Contributor Author

/retest-required

@ashishmax31

Copy link
Copy Markdown
Contributor Author

/test verify-deps

@bryan-cox

Copy link
Copy Markdown
Member

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 16, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aks-4-22
/test e2e-aws-4-22
/test e2e-aks
/test e2e-aws
/test e2e-aws-upgrade-hypershift-operator
/test e2e-azure-v2-self-managed
/test e2e-kubevirt-aws-ovn-reduced
/test e2e-v2-aws
/test e2e-v2-gke

@ashishmax31

Copy link
Copy Markdown
Contributor Author

/test e2e-aks-4-22

@hypershift-jira-solve-ci

Copy link
Copy Markdown

AI Test Failure Analysis

Job: pull-ci-openshift-hypershift-main-e2e-aks | Build: 2066848222243983360 | Cost: $4.4735665000000004 | Failed step: hypershift-azure-run-e2e

View full analysis report


Generated by hypershift-analyze-e2e-failure post-step using Claude claude-opus-4-6

@ashishmax31

Copy link
Copy Markdown
Contributor Author

/retest-required

@ashishmax31

Copy link
Copy Markdown
Contributor Author

/test e2e-kubevirt-aws-ovn-reduced

@hypershift-jira-solve-ci

Copy link
Copy Markdown

Now I have all the evidence I need. Let me produce the final report:

Test Failure Analysis Complete

Job Information

  • Prow Job: pull-ci-openshift-hypershift-main-e2e-kubevirt-aws-ovn-reduced
  • Build ID: 2066940632877764608
  • Target: e2e-kubevirt-aws-ovn-reduced
  • Workflow: hypershift-kubevirt-e2e-aws
  • ci-operator version: v20260616-4220cce81

Test Failure Analysis

Error

/bin/bash: line 12: RELEASE_IMAGE_LATEST: unbound variable

Summary

The ipi-conf pre-phase step failed immediately because the RELEASE_IMAGE_LATEST environment variable was not injected into the step pod, despite releases.latest being correctly defined in the CI configuration and the [release:latest] imagestream being successfully created. This is a ci-operator infrastructure regression introduced in version v20260616-4220cce81 (released today, June 16). The identical failure is reproduced across multiple unrelated PRs (#8312, #8672, #8296, #8579, #8669), confirming it is not caused by PR #8312's code changes. The previous ci-operator version (v20260611-4b8b1c45b, used on June 15) correctly injected RELEASE_IMAGE_LATEST and the ipi-conf step passed.

Root Cause

The root cause is a regression in ci-operator v20260616-4220cce81 that breaks the injection of RELEASE_IMAGE_LATEST environment variable into multi-stage test step pods.

How it should work: The CI configuration (openshift-hypershift-main.yaml) defines releases.latest as an integration stream from ocp/5.0. ci-operator resolves this release, creates the release:latest imagestream tag, and injects the pull spec as RELEASE_IMAGE_LATEST env var into all test step pods. Additionally, the ipi-install-install step in the workflow explicitly declares a dependency {name: "release:latest", env: RELEASE_IMAGE_LATEST}.

What actually happens with the new ci-operator version: The [release:latest] step completes successfully (finished at 18:09:20.858916558Z), but when the ipi-conf pod starts 80 microseconds later (18:09:20.858997460Z), RELEASE_IMAGE_LATEST is not present in the pod's environment. The script runs with set -o nounset and immediately crashes on line 12 when referencing the unbound variable.

Proof this is a ci-operator regression, not a code issue:

Cascade of secondary failures: Because the pre phase fails at ipi-conf, no cluster is provisioned. Post-phase steps (gather-aws-console, aws-deprovision-users-and-policies, aws-deprovision-verification) then fail with CLUSTER_PROFILE_DIR: unbound variable since no cluster profile was set up. The hypershift-k8sgpt step fails with the server doesn't have a resource type "hostedcluster" because no HyperShift operator was installed. These are all expected cascade failures.

Recommendations
  1. This is NOT a PR AROSLSRE-687: propagate HCP Azure resource ID annotation to control plane namespace #8312 issue — no action needed on the PR code. The failure is an infrastructure regression in ci-operator.
  2. Report to CI/Test Platform team — File an issue against openshift/ci-tools reporting that ci-operator v20260616-4220cce81 no longer injects RELEASE_IMAGE_LATEST from releases.latest into multi-stage test step pods. Reference commit 4220cce81 as the likely regression point.
  3. Short-term workaround — Retrigger the job once the ci-operator is rolled back or patched. Alternatively, if the CI team can pin ci-operator to the previous version v20260611-4b8b1c45b, jobs should pass the ipi-conf step again.
  4. Verify scope — Check if other workflows that depend on RELEASE_IMAGE_LATEST (e.g., standard IPI jobs across OpenShift) are also affected. If so, this is a broad CI outage affecting many repositories.
Evidence
Evidence Detail
Primary error /bin/bash: line 12: RELEASE_IMAGE_LATEST: unbound variable in ipi-conf step
Failing step e2e-kubevirt-aws-ovn-reduced-ipi-conf (pre phase, 11s runtime)
ci-operator version (failing) v20260616-4220cce81 (released June 16, 2026)
ci-operator version (working) v20260611-4b8b1c45b (released June 11, 2026)
release:latest created ✅ Yes, at 18:09:20Z — imagestream tag created successfully
RELEASE_IMAGE_LATEST injected ❌ No — env var not present in ipi-conf pod
Same error on PR #8672 ✅ Build 2066936167009357824 — identical RELEASE_IMAGE_LATEST: unbound
Same error on PR #8296 ✅ Build 2066890516695355392 — same day, same ci-operator version
Same error on PR #8579 ✅ Build 2066879015590825984 — same day, same ci-operator version
Yesterday's build passed ipi-conf ✅ Build 2066464708667379712 (PR #8219) — ipi-conf succeeded, failed later at ipi-install
Cascade failures CLUSTER_PROFILE_DIR: unbound in gather-aws-console, aws-deprovision-users-and-policies, aws-deprovision-verification
CI config change Commit 76ba986 (June 12) removed n-minor releases but did NOT modify e2e-kubevirt-aws-ovn-reduced
Workflow unchanged hypershift-kubevirt-e2e-aws workflow last modified September 2025

@bryan-cox

Copy link
Copy Markdown
Member

/override "ci/prow/e2e-kubevirt-aws-ovn-reduced"

This job is permafailing and I pinged the kubevirt folks earlier here - https://redhat-internal.slack.com/archives/C0B71V5TDMW/p1781616231915999

@openshift-ci

openshift-ci Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

@bryan-cox: Overrode contexts on behalf of bryan-cox: ci/prow/e2e-kubevirt-aws-ovn-reduced

Details

In response to this:

/override "ci/prow/e2e-kubevirt-aws-ovn-reduced"

This job is permafailing and I pinged the kubevirt folks earlier here - https://redhat-internal.slack.com/archives/C0B71V5TDMW/p1781616231915999

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@ashishmax31

Copy link
Copy Markdown
Contributor Author

/verified

@openshift-ci-robot

Copy link
Copy Markdown

@ashishmax31: The /verified command must be used with one of the following actions: by, later, remove, or bypass. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

Details

In response to this:

/verified

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Comment thread api/hypershift/v1beta1/hostedcluster_types.go
@devguyio

Copy link
Copy Markdown
Contributor

/hold putting a hold for @enxebre API approval

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 17, 2026
…ane namespace

  Add a new annotation constant HCPAzureResourceIDAnnotation that carries
  the Azure resource ID set by Cluster Service on the HostedCluster CR.
  The hostedcluster controller now propagates this annotation to the
  hosted control plane namespace for Azure platform clusters.

Refer https://redhat.atlassian.net/browse/AROSLSRE-687 and https://issues.redhat.com/browse/AROSLSRE-447 for more details.

Signed-off-by: Ashish <[email protected]>
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Jun 17, 2026
@openshift-ci

openshift-ci Bot commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

New changes are detected. LGTM label has been removed.

@openshift-ci

openshift-ci Bot commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

@ashishmax31: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@ashishmax31

Copy link
Copy Markdown
Contributor Author
demo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/api Indicates the PR includes changes for the API area/hypershift-operator Indicates the PR includes changes for the hypershift operator and API - outside an OCP release do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants