mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-08-02 00:07:50 +00:00
Merge pull request #53397 from andrewsykim/add-kubelet-deprecations
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. add note about kubelet removed flag --api-servers **What this PR does / why we need it**: Adds warning about --api-servers being removed in kubelet in CHANGELOG. This is a breaking change for one of my dev clusters, I imagine others would run into it. **Special notes for your reviewer**: This change was made in https://github.com/kubernetes/kubernetes/pull/40050. cc @mtaufen @liggitt @mikedanese @wojtek-t @kubernetes/sig-cluster-lifecycle-misc @kubernetes/sig-node-misc (just cc'ing the same people in the related PR)
This commit is contained in:
commit
6039c79f6c
@ -667,6 +667,12 @@ Consider the following changes, limitations, and guidelines before you upgrade:
|
||||
|
||||
Don't use these flags. Using deprecated flags causes the server to print a warning. Using a removed flag causes the server to abort the startup.
|
||||
|
||||
* The following deprecated flags were removed from `kubelet`:
|
||||
|
||||
* `api-servers` - add apiserver addresses to the kubeconfig file instead.
|
||||
|
||||
Don't use these flags. Using deprecated flags causes the kubelet to print a warning. Using a removed flag causes the kubelet to abort the startup.
|
||||
|
||||
* StatefulSet: The deprecated `pod.alpha.kubernetes.io/initialized` annotation for interrupting the StatefulSet Pod management is now ignored. StatefulSets with this annotation set to `true` or with no value will behave just as they did in previous versions. Dormant StatefulSets with the annotation set to `false` will become active after upgrading.
|
||||
|
||||
* The CronJob object is now enabled by default at `v1beta1`. CronJob `v2alpha1` is still available, but it must be explicitly enabled. We recommend that you move any current CronJob objects to `batch/v1beta1.CronJob`. Be aware that if you specify the deprecated version, you may encounter Resource Not Found errors. These errors occur because the new controllers look for the new version during a rolling update.
|
||||
|
Loading…
Reference in New Issue
Block a user