-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Post Issuance Check: Certificate's AdditionalOutputFormats #4813
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
Post Issuance Check: Certificate's AdditionalOutputFormats #4813
Conversation
jahrlin
left a comment
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.
LGTM but for the two comments describing the policy checks
Signed-off-by: joshvanl <vleeuwenjoshua@gmail.com>
Signed-off-by: joshvanl <vleeuwenjoshua@gmail.com>
Signed-off-by: joshvanl <vleeuwenjoshua@gmail.com>
Signed-off-by: joshvanl <vleeuwenjoshua@gmail.com>
value in /devel/run-e2e.sh Signed-off-by: joshvanl <vleeuwenjoshua@gmail.com>
27901ac to
f932e80
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JoshVanL The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
f932e80 to
19b68c9
Compare
Signed-off-by: joshvanl <vleeuwenjoshua@gmail.com>
Signed-off-by: joshvanl <vleeuwenjoshua@gmail.com>
|
Thanks @JoshVanL! /lgtm |
This PR adds two Post Issuances checks which are carried out by the secrets manager (issuing controller). Together, they verify that the Certificate's
AdditionalOutputFormatsare correctly reflected on the target secret; they only exist if they should, they contain the correct values, and they must exist if defined on the Certificate.As the same with the Certificate's
SecretTemplate, any violation to the rule will have the Secret re-applied, and the correct key/values added/removed/modified.These checks are not gated behind a feature gate. They don't need to be- the API is only available when that feature gate is enabled. If somehow the Certificate does contain
AdditionalOutputFormatswhen the feature gate is disabled, any violation would cause a re-apply of the Secret and the resulting state reflects no output formats (since the gate is disabled). Any further re-reconcile will not cause a loop- since applying with no state changes does not cause a informer event./kind feature
/milestone v1.8
/area api