OCPBUGS-81161: [release-4.19] fix(cpo): Don't remove HCP Ingress from routes when CapabilityRoute is disabled#8093
Conversation
…s disabled Prevents reconciliation failures on vanilla Kubernetes clusters on IBM Cloud by avoiding route listing operations when Route CRDs are not available.
|
@arolika: This pull request references Jira Issue OCPBUGS-80950, 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. |
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Review skipped — only excluded labels are configured. (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro 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)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Hi @arolika. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
|
/retitle [release-4.19] fix(cpo): Don't remove HCP Ingress from routes when CapabilityRoute is disabled |
|
@arolika: Re-titling can only be requested by trusted users, like repository collaborators. 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 kubernetes-sigs/prow repository. |
|
/retitle [release-4.19] fix(cpo): Don't remove HCP Ingress from routes when CapabilityRoute is disabled |
|
@arolika: 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-80950 |
|
@arolika: Jira Issue OCPBUGS-80950 has been cloned as Jira Issue OCPBUGS-81161. 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. |
|
@arolika: This pull request references Jira Issue OCPBUGS-81161, 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. |
|
/lgtm |
|
@matlaj: 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. |
|
As discussed privately with @matlaj, I verified this PR on IBM Cloud by deploying a version 4.19 hosted cluster with the changes. The fix functions as intended and I observed no regressions. |
|
/retest |
1 similar comment
|
/retest |
|
/jira refresh |
|
@TwoDCube: This pull request references Jira Issue OCPBUGS-81161, which is valid. The bug has been moved to the POST state. 7 validation(s) were run on this bug
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. |
|
/ok-to-test |
|
/retest |
|
@arolika: 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. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: arolika, rtheis, sjenning 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 |
5b151f0
into
openshift:release-4.19
|
@arolika: Jira Issue Verification Checks: Jira Issue OCPBUGS-81161 Jira Issue OCPBUGS-81161 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 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. |
|
Fix included in accepted release 4.19.0-0.nightly-2026-04-07-220324 |
What this PR does / why we need it:
This is a backport PR to
release-4.19branch. I'm opening this because the [cherrypick PR had merge conflicts.](#8083)[Original PR can be found here.](#8001)
On IBM Cloud the
servicePublishingStrategy: Routecan't assume that the management cluster is an OCP cluster, because it still has vanilla k8s management clusters.When running on vanilla Kubernetes on IBM Cloud (which doesn't have Route CRDs), the operator crashes during reconciliation when attempting to list Route resources.
HyperShift on IBM Cloud should work on both OpenShift and vanilla Kubernetes (IBM Cloud) management clusters, gracefully handling the absence of optional APIs like Route.
The fix is an extra check in the
removeHCPIngressFromRoutes()function to return early if the management cluster has no Route capability.Which issue(s) this PR fixes:
Fixes #OCPBUGS-78778
Special notes for your reviewer:
Checklist: