-
Notifications
You must be signed in to change notification settings - Fork 707
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
Create one transport certificates Secret per StatefulSet #3828
Create one transport certificates Secret per StatefulSet #3828
Conversation
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.
Looks good to me! Much less invasive change than I initially thought. Is it worth backporting this to 1.3?
pkg/controller/elasticsearch/certificates/transport/reconcile.go
Outdated
Show resolved
Hide resolved
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! I did some tests and could not find a flaw.
I think I would be 👍 once I see all the e2e tests green. |
With this PR the transport certificates are stored in one Secret per
nodeSet
/StatefulSet
.Secret
is deleted only when the StatefulSets specifications have been updated (I did some tests and it seems to be fine to delete a Secret which is used by a Pod, the content is still available until the Pod is deleted).Secrets
are named*-transport-certs
and not*-transport-certificates
to save a few characters and be consistent with otherSecrets
(*-[http|transport]-certs-public
,*-[http|transport]-certs-internal
)Fixes (or only mitigates ?) #3734