-
Notifications
You must be signed in to change notification settings - Fork 683
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
Allow to disable secret auto-recreation #1118
Conversation
07a963b
to
37ae31f
Compare
Signed-off-by: Jose Luis Vazquez Gonzalez <[email protected]>
37ae31f
to
ac73912
Compare
Signed-off-by: Jose Luis Vazquez Gonzalez <[email protected]>
f2d971f
to
b866e6a
Compare
Signed-off-by: Jose Luis Vazquez Gonzalez <[email protected]>
f54fd26
to
5325e94
Compare
Co-authored-by: Alejandro Moreno <[email protected]> Signed-off-by: josvaz <[email protected]>
$ helm template helm/sealed-secrets/ --set skipRecreate=true |grep args -A 5
args:
- --update-status
- --skip-recreate
- --key-prefix
- "sealed-secrets-key"
image: docker.io/bitnami/sealed-secrets-controller:v0.19.5 |
f1958dc
to
d73a487
Compare
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
Signed-off-by: Jose Luis Vazquez Gonzalez <[email protected]>
d73a487
to
3cebdeb
Compare
Co-authored-by: Alejandro Moreno <[email protected]> Signed-off-by: josvaz <[email protected]> Signed-off-by: Jose Luis Vazquez Gonzalez <[email protected]>
24788dd
to
1e03569
Compare
@@ -56,6 +56,12 @@ secretName: "sealed-secrets-key" | |||
## @param updateStatus Specifies whether the Sealed Secrets controller should update the status subresource | |||
## | |||
updateStatus: true | |||
## @param skipRecreate Specifies whether the Sealed Secrets controller should skip recreating removed secrets | |||
## Setting it to false allows to optionally restore backward compatibility in low priviledge |
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.
Just noticed this small typo ^^
This message is talking about the case in which skipRecreate
is actually set to true
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.
Fixed per #1371
Description of the change
Add a new recreate flag, on by default, that when switched off allows to opt in for lost backward compatibility after the introduction of automatic secret recreation by PR #963.
Benefits
Some low privilege environment do not allow users to watch secrets, so this will allow them to still install sealed secrets just by using the new recreate flag set to
false
.Possible drawbacks
It is still a manual fix, as we want it to be a explicit opt in. Also the error about lack of permissions for watching secrets will not point you to this flag. But still this flag should help as it skips secrets watching completely.
Applicable issues
Additional information
Reported at #1064