Skip to content

OCPBUGS-84939: [release-4.22] add CP pull-secret watches for in-place propagation#8408

Open
enxebre wants to merge 1 commit intoopenshift:release-4.22from
enxebre:enxebre/backport-pull-secret-watches-4.22
Open

OCPBUGS-84939: [release-4.22] add CP pull-secret watches for in-place propagation#8408
enxebre wants to merge 1 commit intoopenshift:release-4.22from
enxebre:enxebre/backport-pull-secret-watches-4.22

Conversation

@enxebre
Copy link
Copy Markdown
Member

@enxebre enxebre commented May 4, 2026

Summary

  • Backport of controller changes from OCPBUGS-84528: clarify pull secret in-place update behavior and add CP watches #8327 to release-4.22
  • Adds CP namespace pull-secret watches to both the globalps and resources HCCO controllers
  • Ensures in-place updates to HostedCluster.spec.pullSecret propagate promptly to the guest cluster (kube-system/original-pull-secret and openshift-config/pull-secret) without depending on incidental kube-system secret activity

Test plan

  • Verify e2e-aks-4-22 passes (the in-place propagation test is skipped on CPO < 4.23 in the main branch, so this backport makes the behavior correct for 4.22 CPO)
  • Verify no regressions in pull secret reconciliation

🤖 Generated with Claude Code

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 4, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 4, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 04fe08ff-2681-47ad-8e72-98b4decbd44c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

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

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

@openshift-ci-robot
Copy link
Copy Markdown

@enxebre: This pull request references Jira Issue OCPBUGS-84528, which is invalid:

  • expected the bug to target either version "4.22." or "openshift-4.22.", but it targets "5.0" instead
  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-84528 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

  • Backport of controller changes from OCPBUGS-84528: clarify pull secret in-place update behavior and add CP watches #8327 to release-4.22
  • Adds CP namespace pull-secret watches to both the globalps and resources HCCO controllers
  • Ensures in-place updates to HostedCluster.spec.pullSecret propagate promptly to the guest cluster (kube-system/original-pull-secret and openshift-config/pull-secret) without depending on incidental kube-system secret activity

Test plan

  • Verify e2e-aks-4-22 passes (the in-place propagation test is skipped on CPO < 4.23 in the main branch, so this backport makes the behavior correct for 4.22 CPO)
  • Verify no regressions in pull secret reconciliation

🤖 Generated with Claude Code

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.

@openshift-ci openshift-ci Bot requested review from bryan-cox and cblecker May 4, 2026 12:16
@openshift-ci openshift-ci Bot added area/control-plane-operator Indicates the PR includes changes for the control plane operator - in an OCP release approved Indicates a PR has been approved by an approver from all required OWNERS files. and removed do-not-merge/needs-area labels May 4, 2026
@enxebre enxebre force-pushed the enxebre/backport-pull-secret-watches-4.22 branch from 1a26a70 to 031c695 Compare May 4, 2026 12:17
@openshift-ci openshift-ci Bot added area/api Indicates the PR includes changes for the API area/cli Indicates the PR includes changes for CLI area/documentation Indicates the PR includes changes for documentation labels May 4, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 4, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: enxebre

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

@enxebre enxebre changed the title OCPBUGS-84528: [release-4.22] add CP pull-secret watches for in-place propagation [release-4.22] add CP pull-secret watches for in-place propagation May 4, 2026
@openshift-ci-robot openshift-ci-robot removed jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 4, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@enxebre: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

Summary

  • Backport of controller changes from OCPBUGS-84528: clarify pull secret in-place update behavior and add CP watches #8327 to release-4.22
  • Adds CP namespace pull-secret watches to both the globalps and resources HCCO controllers
  • Ensures in-place updates to HostedCluster.spec.pullSecret propagate promptly to the guest cluster (kube-system/original-pull-secret and openshift-config/pull-secret) without depending on incidental kube-system secret activity

Test plan

  • Verify e2e-aks-4-22 passes (the in-place propagation test is skipped on CPO < 4.23 in the main branch, so this backport makes the behavior correct for 4.22 CPO)
  • Verify no regressions in pull secret reconciliation

🤖 Generated with Claude Code

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.

@enxebre
Copy link
Copy Markdown
Member Author

enxebre commented May 4, 2026

/jira cherry-pick OCPBUGS-84528

@openshift-ci-robot
Copy link
Copy Markdown

@enxebre: Jira Issue OCPBUGS-84528 has been cloned as Jira Issue OCPBUGS-84939. Will retitle bug to link to clone.
/retitle OCPBUGS-84939: [release-4.22] add CP pull-secret watches for in-place propagation

Details

In response to this:

/jira cherry-pick OCPBUGS-84528

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.

@openshift-ci openshift-ci Bot changed the title [release-4.22] add CP pull-secret watches for in-place propagation OCPBUGS-84939: [release-4.22] add CP pull-secret watches for in-place propagation May 4, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 4, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@enxebre: This pull request references Jira Issue OCPBUGS-84939, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-84528 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST instead
  • expected dependent Jira Issue OCPBUGS-84528 to target a version in 5.0.0, but it targets "5.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

  • Backport of controller changes from OCPBUGS-84528: clarify pull secret in-place update behavior and add CP watches #8327 to release-4.22
  • Adds CP namespace pull-secret watches to both the globalps and resources HCCO controllers
  • Ensures in-place updates to HostedCluster.spec.pullSecret propagate promptly to the guest cluster (kube-system/original-pull-secret and openshift-config/pull-secret) without depending on incidental kube-system secret activity

Test plan

  • Verify e2e-aks-4-22 passes (the in-place propagation test is skipped on CPO < 4.23 in the main branch, so this backport makes the behavior correct for 4.22 CPO)
  • Verify no regressions in pull secret reconciliation

🤖 Generated with Claude Code

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.

@codecov
Copy link
Copy Markdown

codecov Bot commented May 4, 2026

Codecov Report

❌ Patch coverage is 50.00000% with 12 lines in your changes missing coverage. Please review.
✅ Project coverage is 34.79%. Comparing base (7c6d1fb) to head (98bfce0).

Files with missing lines Patch % Lines
...lusterconfigoperator/controllers/globalps/setup.go 53.33% 7 Missing ⚠️
...rconfigoperator/controllers/resources/resources.go 44.44% 5 Missing ⚠️
Additional details and impacted files
@@              Coverage Diff              @@
##           release-4.22    #8408   +/-   ##
=============================================
  Coverage         34.79%   34.79%           
=============================================
  Files               767      767           
  Lines             93445    93467   +22     
=============================================
+ Hits              32511    32523   +12     
- Misses            58255    58265   +10     
  Partials           2679     2679           
Files with missing lines Coverage Δ
...rconfigoperator/controllers/resources/resources.go 50.50% <44.44%> (-0.02%) ⬇️
...lusterconfigoperator/controllers/globalps/setup.go 10.25% <53.33%> (+10.25%) ⬆️
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@enxebre enxebre force-pushed the enxebre/backport-pull-secret-watches-4.22 branch from 031c695 to 2c464f6 Compare May 4, 2026 13:09
@cblecker
Copy link
Copy Markdown
Member

cblecker commented May 5, 2026

/uncc

@openshift-ci openshift-ci Bot removed the request for review from cblecker May 5, 2026 15:40
Add watches on the control plane namespace pull-secret in both the
globalps and resources HCCO controllers so that in-place updates to
HostedCluster.spec.pullSecret propagate promptly to the guest cluster
without depending on incidental kube-system secret activity.

Also clarify the spec.pullSecret API godoc to document the in-place
update behavior for AWS and Azure Replace-strategy NodePools.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@enxebre enxebre force-pushed the enxebre/backport-pull-secret-watches-4.22 branch from f124e5b to 98bfce0 Compare May 8, 2026 07:57
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 8, 2026

@enxebre: 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.

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/cli Indicates the PR includes changes for CLI area/control-plane-operator Indicates the PR includes changes for the control plane operator - in an OCP release area/documentation Indicates the PR includes changes for documentation jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. 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.

4 participants