OCPBUGS-88037: Set cluster ownership label on GCPCluster#591
Conversation
|
@matzew: This pull request references Jira Issue OCPBUGS-88037, 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. |
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Set the kubernetes-io-cluster-<infraID>=owned label on the GCPCluster object via AdditionalLabels so that CAPI-created GCP resources are visible to the installer's destroy logic. GCP label keys only permit lowercase letters, hyphens, and underscores. Also propagate user-defined resource labels from Infrastructure.Status.PlatformStatus.GCP.ResourceLabels and resource manager tags from GCP.ResourceTags to match MAPI behaviour. Without this label, openshift-install destroy cluster cannot identify CAPI-created resources and they are leaked. Signed-off-by: Matthias Wessendorf <mwessend@redhat.com>
7be4727 to
0de7612
Compare
|
Warning Review limit reached
More reviews will be available in 23 minutes and 48 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
✨ 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 |
|
@matzew: 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. |
Set the kubernetes-io-cluster-=owned label on the GCPCluster object via AdditionalLabels so that CAPI-created GCP resources are visible to the installer's destroy logic. GCP label keys only permit lowercase letters, hyphens, and underscores. Also propagate user-defined resource labels from Infrastructure.Status.PlatformStatus.GCP.ResourceLabels and resource manager tags from GCP.ResourceTags to match MAPI behaviour.
Without this label, openshift-install destroy cluster cannot identify CAPI-created resources and they are leaked.