Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
BUGFIX: issuer-ref and certificate-name annotations are incorrectly updated on Secrets #6147
BUGFIX: issuer-ref and certificate-name annotations are incorrectly updated on Secrets #6147
Changes from 1 commit
8ddf016
3aa7b82
9c9e833
fe4f4e4
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These 4 fields are now set by the
setValues
function.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We now explicitly pass the CertificateName, IssuerName, IssuerKind and IssuerGroup values to setValues instead of reading these values from the cmapi.Certificate resource, since cmapi.Certificate might have been updated since the secret was created.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed the order: first, we apply the SecretTemplate; afterwards, we apply the cert-manager annotations.
This prevents us from overwriting cert-manager annotations using the SecretTemplate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm sure that this was the original behaviour when @jonathansp originally created the feature. See
I wonder when and how this bug got introduced?
Which versions are affected? Do we need to fix this bug in a separate PR and backport to the affected versions?
Is there a unit test for this? If not, please add one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This issue was introduced in #4746
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Previously,
AnnotationsForCertificate
was setting these annotations. In this PR, I moved that step out of theAnnotationsForCertificate
function, since it now uses values from thedata
object.