-
Notifications
You must be signed in to change notification settings - Fork 455
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 reload CA cert in operator-ca-tls
secret
#1716
Bugfix reload CA cert in operator-ca-tls
secret
#1716
Conversation
operator-ca-tls
secret
This PR needs slices library released in go 1.21, once this PR #1718 is merged it should pass tests |
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
fe69c09
to
ca465c4
Compare
When the CA certificate in the secret `operator-ca-tls` changes, Operator recreates this secret on the Tenants namespace, but is not using the newly provided cert for healthcheck, this will force reload the certificates on secret update
ca465c4
to
735dbfa
Compare
PTAL @cesnietor @cniackz @dvaldivia |
Signed-off-by: pjuarezd <pjuarezd@users.noreply.github.com>
Signed-off-by: pjuarezd <pjuarezd@users.noreply.github.com>
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, thanks for addressing the comments.
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
When the CA certificate in the secret
operator-ca-tls
changes, Operator recreates this secret on the Tenants namespace, but is not using the newly provided cert for healthcheck, a manual operator deployment restart is required.This fix will force reload the certificates on secret update.