Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 fix: considers objects in kube-system for cert-manager to avoid upgrading twice #28

Merged
merged 1 commit into from
Oct 31, 2024

Conversation

faiq
Copy link

@faiq faiq commented Oct 29, 2024

What this PR does / why we need it:
Downstream of kubernetes-sigs#11351

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

@dkoshkin dkoshkin changed the base branch from main to d2iq/release-1.8.4 October 29, 2024 20:56
@dkoshkin dkoshkin changed the base branch from d2iq/release-1.8.4 to main October 29, 2024 20:57
@faiq faiq force-pushed the faiq/fix-clusterctl-cert-manager branch from ded6366 to 6d2359d Compare October 29, 2024 21:00
@faiq faiq changed the base branch from main to d2iq/release-1.8.4 October 29, 2024 21:00
Copy link

@supershal supershal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@faiq faiq force-pushed the faiq/fix-clusterctl-cert-manager branch from 6d2359d to a3c4987 Compare October 31, 2024 17:24
@faiq faiq force-pushed the faiq/fix-clusterctl-cert-manager branch from a3c4987 to cf94a10 Compare October 31, 2024 18:33
@faiq faiq changed the title fix: considers objects in kube-system for cert-manager to avoid upgrading twice 🐛 fix: considers objects in kube-system for cert-manager to avoid upgrading twice Oct 31, 2024
@faiq faiq merged commit 9890391 into d2iq/release-1.8.4 Oct 31, 2024
9 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants