GCP-958: re-enable GCP PD CSI driver in HyperShift path - #742
Conversation
The HostedCluster/CVO side wiring (CVO resource exclusion and the control-plane sub-deployment image env var) has landed in openshift/hypershift, and end-to-end dynamic PD provisioning has been verified on a HyperShift hosted cluster. Re-register GCP PD in HyperShiftStarter.populateConfigs() so CSO activates the driver operator on GCP HostedClusters again. This reverts the temporary disable from 26ededa (GCP-958). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
@ckandag: This pull request references GCP-958 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.1.0" version, but no target version was set. 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. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. WalkthroughHyperShift now enables the GCP Persistent Disk CSI operator configuration in the operator starter. ChangesGCP PD CSI operator
Priority: ➖ Normal Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to HyperShift GCP clusters will again enable the GCP Persistent Disk CSI driver; no current merge-blocking risk remains. Suggested reviewers: 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/pipeline required |
|
Scheduling required tests: |
|
/verified by @ckandag |
|
@ckandag: This PR has been marked as verified by 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. |
|
We had to earlier disable GCP in CSO because Hypershift repo changes for GCP-PD needed to go in first. With both Hypershift changes and RBAC fix in csi-driver merged, reenabling GCP in CSO. cc @rhrmo PTAL |
|
/test hypershift-aws-e2e-external |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ckandag, rhrmo 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 |
|
/test hypershift-aws-e2e-external |
2 similar comments
|
/test hypershift-aws-e2e-external |
|
/test hypershift-aws-e2e-external |
|
@ckandag: The following test failed, say
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. |
|
@rhrmo: aws test appears to be in perm fail situation, would it be possible to get an override for this test. |
What
Re-registers the GCP PD CSI driver in
HyperShiftStarter.populateConfigs()so CSO activates the driver operator on GCP HostedClusters again. This un-comments the single line that was temporarily disabled in #739 (commit26ededa83).Why now
#739 disabled GCP PD on the HyperShift path because the HostedCluster/CVO-side wiring had not yet landed in openshift/hypershift, and the csi-operator applied a set of prerequisite RBAC assets via the management-cluster client that it lacked permission for — which crash-looped the operator and hung ClusterVersion.
Both root causes are now addressed:
controller_sa.yaml).Verification
End-to-end dynamic provisioning was verified on a GCP HyperShift hosted cluster running a CSO build with GCP PD enabled:
storageClusterOperatorAvailable=True, Progressing=False, Degraded=Falsegcp-pd-csi-driver-nodeDaemonSet running on all workers (3/3 per pod)standard-csi,pd.csi.storage.gke.io) → Bound; PV dynamically provisionedREADY, attached to the scheduled worker node)Completed/Available=TrueThis reverts the temporary disable from
26ededa83(GCP-958). Standalone GCP PD support is unaffected.Summary by CodeRabbit
New Features
Bug Fixes