OCPBUGS-84939: [release-4.22] add CP pull-secret watches for in-place propagation#8408
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@enxebre: This pull request references Jira Issue OCPBUGS-84528, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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. |
1a26a70 to
031c695
Compare
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@enxebre: No Jira issue is referenced in the title of this pull request. DetailsIn response to this:
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. |
|
/jira cherry-pick OCPBUGS-84528 |
|
@enxebre: Jira Issue OCPBUGS-84528 has been cloned as Jira Issue OCPBUGS-84939. Will retitle bug to link to clone. DetailsIn response to this:
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: This pull request references Jira Issue OCPBUGS-84939, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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 Report❌ Patch coverage is
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
🚀 New features to boost your workflow:
|
031c695 to
2c464f6
Compare
|
/uncc |
2c464f6 to
f124e5b
Compare
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>
f124e5b to
98bfce0
Compare
|
@enxebre: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
Summary
globalpsandresourcesHCCO controllersHostedCluster.spec.pullSecretpropagate promptly to the guest cluster (kube-system/original-pull-secretandopenshift-config/pull-secret) without depending on incidental kube-system secret activityTest plan
e2e-aks-4-22passes (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)🤖 Generated with Claude Code