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: prevent recurring helm install/upgrade creating a loop deleting caBundle, when certManager is enabled #309

Merged
merged 1 commit into from
Jan 25, 2024

Conversation

rsafonseca
Copy link
Contributor

Overview

Whenever cert-manager is used to generate the certificate and set the caBundle in the webhook, on recurring executions of helm the caBundle is deleted, and later re-added.

This PR disables handling of the caBundle property of the webhook in case cert-manager is being used, to prevent this issue.

…caBundle, when certManager is enabled

Signed-off-by: Rafael da Fonseca <[email protected]>
@rsafonseca rsafonseca requested a review from a team as a code owner January 24, 2024 10:35
@rsafonseca rsafonseca requested review from akijakya and removed request for a team January 24, 2024 10:35
@github-actions github-actions bot added the size/XS Denotes a PR that changes 0-9 lines label Jan 24, 2024
Copy link
Member

@akijakya akijakya left a comment

Choose a reason for hiding this comment

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

Thanks for the contribution!

@akijakya akijakya requested a review from ramizpolic January 25, 2024 16:29
Copy link
Member

@ramizpolic ramizpolic left a comment

Choose a reason for hiding this comment

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

Nice catch, thanks for the correction!

@ramizpolic ramizpolic merged commit f1c5d77 into bank-vaults:main Jan 25, 2024
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/XS Denotes a PR that changes 0-9 lines
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants