-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Move rotating kubelet client certificate to beta. #51045
Move rotating kubelet client certificate to beta. #51045
Conversation
jcbsmpsn
commented
Aug 21, 2017
pkg/features/kube_features.go
Outdated
@@ -152,7 +152,7 @@ var defaultKubernetesFeatureGates = map[utilfeature.Feature]utilfeature.FeatureS | |||
Accelerators: {Default: false, PreRelease: utilfeature.Alpha}, | |||
TaintBasedEvictions: {Default: false, PreRelease: utilfeature.Alpha}, | |||
RotateKubeletServerCertificate: {Default: false, PreRelease: utilfeature.Alpha}, | |||
RotateKubeletClientCertificate: {Default: false, PreRelease: utilfeature.Alpha}, | |||
RotateKubeletClientCertificate: {Default: false, PreRelease: utilfeature.Beta}, |
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.
Shouldn't this default to true?
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.
So, I'd like to set the default value for the flag to true, which would turn this feature on by default when it goes GA. Leaving this value false which the feature is beta would mean people won't get the beta feature enabled by default.
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.
What's the timeline for GA? I'd imagine most setups will still use static TLS for the foreseeable future and it seems odd to turn it on by default if a cluster isn't using it.
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.
what is the behavior if the controller manager doesn't have a signing CA set up? does this degrade gracefully if unable to submit the CSR, or if the submitted CSR is never approved?
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.
I mis-understood the behavior of the signing CA. I'm going to turn the flag to false by default, and put the beta feature to true.
cmd/kubelet/app/options/options.go
Outdated
@@ -203,6 +205,8 @@ func (f *KubeletFlags) AddFlags(fs *pflag.FlagSet) { | |||
"If the file specified by --kubeconfig does not exist, the bootstrap kubeconfig is used to request a client certificate from the API server. "+ | |||
"On success, a kubeconfig file referencing the generated client certificate and key is written to the path specified by --kubeconfig. "+ | |||
"The client certificate and key file will be stored in the directory pointed by --cert-dir.") | |||
fs.BoolVar(&f.RotateCertificates, "rotate-certificates", f.RotateCertificates, "<Warning: Beta feature> Auto rotate the kubelet client certificates by requesting new certificates from the kube-apiserver when the certificate expiration approaches.") | |||
fs.MarkHidden("rotate-certificates") // Mark this flag as hidden because it is still in Beta. |
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.
Has this pattern been used elsewhere? I don't remember us hiding other flags.
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.
I don't know of it existing anywhere else. You think just the warning text and not hiding it is the best way to go?
cc @kubernetes/sig-auth-pr-reviews |
964ab0a
to
e74416b
Compare
/lgtm |
/assign @dchen1107 For approval. |
/approve no-issue |
/test all Tests are more than 96 hours old. Re-running tests. |
e74416b
to
b11bdc0
Compare
/assign @smarterclayton Do you have any time to review this for approval? |
/approve |
b11bdc0
to
a0d81d1
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ericchiang, jcbsmpsn, mikedanese, smarterclayton Associated issue requirement bypassed by: mikedanese The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Automatic merge from submit-queue (batch tested with PRs 49961, 50005, 50738, 51045, 49927) |