Skip to content
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

Merged

Conversation

barkbay
Copy link
Contributor

@barkbay barkbay commented Oct 13, 2020

With this PR the transport certificates are stored in one Secret per nodeSet/StatefulSet.

  • Current/legacy transport certs 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).
  • Unit tests have been added in order to test the new behaviour.
  • Transport certs Secrets are named *-transport-certs and not *-transport-certificates to save a few characters and be consistent with other Secrets (*-[http|transport]-certs-public,*-[http|transport]-certs-internal)

Fixes (or only mitigates ?) #3734

@barkbay barkbay added >enhancement Enhancement of existing functionality v1.4.0 labels Oct 13, 2020
Copy link
Collaborator

@pebrc pebrc left a 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/apis/elasticsearch/v1/name.go Outdated Show resolved Hide resolved
Copy link
Collaborator

@pebrc pebrc left a 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.

@barkbay
Copy link
Contributor Author

barkbay commented Oct 15, 2020

Is it worth backporting this to 1.3?

I think I would be 👍 once I see all the e2e tests green.
Any opinion on that @david-kow ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>enhancement Enhancement of existing functionality v1.4.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants