added etcd CA and client certificate support #3562
Draft
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
vardhaman22
force-pushed
the
etcd-ca-and-client-cert
branch
from
bc2b833
to
3adfd28
Compare
vardhaman22
force-pushed
the
etcd-ca-and-client-cert
branch
from
3adfd28
to
05014a1
Compare
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.
new etcd CA cert and kube API client for etcd will only be used for clusters >v1.29 k8s versions.
Note: the SemVerK8sVersion129OrHigher constant value is set to >=1.28.0-rancher0 for testing only