-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
kubeadm: mark the phase 'experimental-cert-rotation' as deprecated #124419
kubeadm: mark the phase 'experimental-cert-rotation' as deprecated #124419
Conversation
/triage accepted |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: neolit123 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
searching on github i found a couple of shell scripts that use the deprecated phase directly. the plan is to remove it in 1.32. |
Out of
That's OK for deprecating an experimental phase. Or a later release. Either is OK to me. LGTM leave to @SataQiu to take a look. |
not from k / k-sigs orgs.
as per the rules we can remove it without deprecation. but if something says alpha or expirimental for a long time and is used in user scripts and production, then it's not alpha / experimental anymore. a great example is kube-proxy's v1alpha1 config. |
Changelog suggestion -kubeadm: mark the sub-phase of 'init kubelet-finilize' called 'experimental-cert-rotation' as deprecated and print a warning if its used directly. It will be removed in a future release. Add a replacement phase 'enable-client-cert-rotation'.
+kubeadm: marked a sub-phase of `kubeadm init kubelet-finalize`, named `experimental-cert-rotation`, as deprecated;
+it will be removed in a future release.
+The kubeadm tool now prints a warning if that deprecated sub-phase is used directly.
+Added a replacement sub-phase: `enable-client-cert-rotation`. |
/lgtm |
LGTM label has been added. Git tree hash: 17cafb4d77c8b95bda59c0f7a305dc108f4ba9aa
|
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.
SGTM
if enableClientCertRotationRun { | ||
return nil | ||
} | ||
klog.Warning("The phase 'experimental-cert-rotation' is deprecate and will be removed in a future release. " + |
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.
klog.Warning("The phase 'experimental-cert-rotation' is deprecate and will be removed in a future release. " + | |
klog.Warning("The phase 'experimental-cert-rotation' is deprecated and will be removed in a future release. " + |
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.
updated.
- Mark the phase 'init kubelet-finilize experimental-cert-rotation' as deprecated and print a warning if its used directly. It should be removed in 1.32. - Add a replacement phase 'enable-client-cert-rotation'. (!!) We should stop using the 'experimental' and 'alpha' names for phases, clI flags and k8s object names as this complicates the graduation and users will use the feature in production regardless. Having a 'DEPRECATED' or 'EXPERIMENTAL' text in descriptions is sufficient to indicate a status of a feature that should not be used in production.
518c51a
to
6e17cc7
Compare
/retest |
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
LGTM label has been added. Git tree hash: 70636b90e5a2fb9003b1a0644fa4afc8668548d0
|
/unhold |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
What type of PR is this?
/kind cleanup deprecation
What this PR does / why we need it:
(!!) We should stop using the 'experimental' and 'alpha' words in phases, clI flags and k8s object names as this complicates the graduation and users will use the feature in production regardless.
Having a 'DEPRECATED' or 'EXPERIMENTAL' text in descriptions is sufficient to indicate a status of a feature that should not be used in production.
Which issue(s) this PR fixes:
xref kubernetes/kubeadm#3046
Special notes for your reviewer:
NONE
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: