Upgrade etcd for etcd proxy pods to v3.3.8 #38
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
xmudrii
added
the
ready-for-review
5 tasks
sttts
approved these changes
Jul 2, 2018
|
Created a PR to propose backporting the TLS/SSL feature to etcd v3.2 (etcd-io/etcd#9894). In meanwhile, we can merge the PR, and get back to v3.2 if the PR gets accepted to be fully compatible with Kubernetes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR upgrades Etcd for etcd proxy pods to v3.3.8 from v3.2.18.
This is because v3.2 doesn't have flags for specifying CA certificate and server certificate and key. The v3.3 introduces several new flags, including
--trusted-ca-file,--cert-file,--key-file, that we'll use to handle SSL for the etcd proxy.The E2E tests are passing with this build.
Required by #35
/cc @deads2k @sttts