forked from kubernetes/website
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add initial v1.26 deprecations and removals blog
- Loading branch information
Showing
1 changed file
with
116 additions
and
0 deletions.
There are no files selected for viewing
116 changes: 116 additions & 0 deletions
116
content/en/blog/_posts/2022-10-18-kubernetes-1.26-deprecations-and-removals.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,116 @@ | ||
| --- | ||
| layout: blog | ||
| title: "Kubernetes Removals, Deprecations, and Major Changes in 1.26" | ||
| date: 2022-11-18 | ||
| slug: upcoming-changes-in-kubernetes-1-26 | ||
| --- | ||
|
|
||
| **Authors**: Frederico Muñoz | ||
|
|
||
| Change is an integral part of the Kubernetes life-cycle: as Kubernetes grows and matures, features may be deprecated, removed, or replaced with improvements for the health of the project. For Kubernetes v1.26 there are several planned: this article identifies and describes some of them, based on the information available at this mid-cycle point in the v1.26 release process, which is still ongoing and can introduce additional changes. | ||
|
|
||
| ## The Kubernetes API Removal and Deprecation process {#k8s-api-deprecation-process} | ||
|
|
||
| The Kubernetes project has a [well-documented deprecation policy](https://kubernetes.io/docs/reference/using-api/deprecation-policy/) for features. This policy states that stable APIs may only be deprecated when a newer, stable version of that same API is available and that APIs have a minimum lifetime for each stability level. A deprecated API is one that has been marked for removal in a future Kubernetes release; it will continue to function until removal (at least one year from the deprecation), but usage will result in a warning being displayed. Removed APIs are no longer available in the current version, at which point you must migrate to using the replacement. | ||
|
|
||
| * Generally available (GA) or stable API versions may be marked as deprecated but must not be removed within a major version of Kubernetes. | ||
| * Beta or pre-release API versions must be supported for 3 releases after deprecation. | ||
| * Alpha or experimental API versions may be removed in any release without prior deprecation notice. | ||
|
|
||
| Whether an API is removed as a result of a feature graduating from beta to stable or because that API simply did not succeed, all removals comply with this deprecation policy. Whenever an API is removed, migration options are communicated in the documentation. | ||
|
|
||
|
|
||
| ## A note about Dynamic Kubelet configuration {#dynamic-kubelet-removal} | ||
|
|
||
| Dynamic Kubelet Configuration allowed [new Kubelet configurations to be rolled out in a live cluster](https://github.com/kubernetes/enhancements/tree/2cd758cc6ab617a93f578b40e97728261ab886ed/keps/sig-node/281-dynamic-kubelet-configuration), by enabling specifying the source of the node's configuration for the `DynamicKubeletConfig` feature. | ||
|
|
||
| As mentioned above, the Kubernetes release cycle is live, dynamic, and based on a set of principles, including the [avoidance of permanent beta features](https://kubernetes.io/blog/2020/08/21/moving-forward-from-beta/#avoiding-permanent-beta). With that principle in mind, Dynamic Kubelet Configuration was removed from kubelet in v1.24, [and will be removed from the API server in this release](https://github.com/kubernetes/kubernetes/pull/112643). | ||
|
|
||
| ## Deprecations and removals in Kubernetes v1.26 | ||
|
|
||
| In addition to the above, Kubernetes v1.26 is targeted to include several additional removals and deprecations. | ||
|
|
||
| ### Removal of kube-proxy userspace modes | ||
|
|
||
| After two releases of deprecation, [kube-proxy userspace mode will be removed](https://github.com/kubernetes/kubernetes/pull/112133) in this version; users that have not yet done so are strongly advised to adopt supported approaches, namely the use of `iptables` or `ipvs`on Linux, or `kernelspace` on Windows. | ||
|
|
||
| ### Removal of the `v1beta1` flow control resources API | ||
|
|
||
| The `flowcontrol.apiserver.k8s.io/v1beta1` API version of FlowSchema and PriorityLevelConfiguration [will no longer be served in v1.26](https://kubernetes.io/docs/reference/using-api/deprecation-guide/#flowcontrol-resources-v126). Users should migrate manifests and API clients to use the `flowcontrol.apiserver.k8s.io/v1beta2` API version, available since v1.23. | ||
|
|
||
| ### Removal of the `v2beta2` HorizontalPodAutoscaler API | ||
|
|
||
| The `autoscaling/v2beta2` API version of HorizontalPodAutoscaler [will no longer be served in v1.26](https://kubernetes.io/docs/reference/using-api/deprecation-guide/#horizontalpodautoscaler-v126). Users should migrate manifests and API clients to use the `autoscaling/v2` API version, available since v1.23. | ||
|
|
||
| ### Removal of in-tree credential management code | ||
|
|
||
| In this release, vendor-specific authentication code (i.e. used for authentication against GKE or AKS) [will be removed](https://github.com/kubernetes/kubernetes/pull/112341) from both `client-go` and `kubectl`, being replaced by a plugin architecture. Additional guidance on how to proceed is available for [Azure](https://github.com/Azure/kubelogin) and [Google Cloud](https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke). | ||
|
|
||
| ### Removal of `kube-proxy` userspace modes | ||
|
|
||
| The `userspace` proxy mode, deprecated for over a year, is [no longer supported on either Linux or Windows](https://github.com/kubernetes/kubernetes/pull/112133) and will be removed in this release. Users should use `iptables` or `ipvs` on Linux, or `kernelspace` on Windows: using `--mode userspace` will now fail. | ||
|
|
||
| ### Removal of in-tree OpenStack cloud provider | ||
|
|
||
| The in-tree cloud provider for OpenStack (and the Cinder volume provider) [will be removed](https://github.com/kubernetes/kubernetes/pull/67782). Users are advised to use the external cloud provider and CSI driver from https://github.com/kubernetes/cloud-provider-openstack instead. | ||
|
|
||
| ### Deprecation of non-inclusive `kubectl` flag | ||
|
|
||
| A part of the implementation effort of the [Inclusive Naming Initiative](https://www.cncf.io/announcements/2021/10/13/inclusive-naming-initiative-announces-new-community-resources-for-a-more-inclusive-future/), the `--prune-whitelist` flag [will be deprecated](https://github.com/kubernetes/kubernetes/pull/113116), and replaced with `--prune-allowlist`. Users that use this flag are strongly advised to make the necessary changes prior to the final removal of the flag, in a future release. | ||
|
|
||
| ### Deprecations of `kube-apiserver` flag | ||
|
|
||
| The `master-service-namespace` flag was [already deprecated](https://github.com/kubernetes/kubernetes/pull/112797) and doesn't have any effect, so we do not expect any impact from this deprecation. It will nonetheless be explicitly marked as deprecated in v1.26, preparing the removal in a future release. | ||
|
|
||
| ### Deprecation of several unused `kubectl run` flags | ||
|
|
||
| Several unused flags will be [marked as deprecated](https://github.com/kubernetes/kubernetes/pull/112261), including: | ||
|
|
||
| * `--cascade` | ||
| * `--filename` | ||
| * `--force` | ||
| * `--grace-period` | ||
| * `--kustomize` | ||
| * `--recursive` | ||
| * `--timeout` | ||
| * `--wait` | ||
|
|
||
| These flags are already ignored so no impact is expected: the explicit deprecation sets a warning message and prepares the removal of the flags in a future release. | ||
|
|
||
| ### Removal of deprecated klog flags | ||
|
|
||
| This change completes the [deprecations of `klogs` flags](https://github.com/kubernetes/kubernetes/pull/112120) which are no longer supported, and have been removed from Kubernetes components. | ||
|
|
||
|
|
||
| ## Additional changes for Kubernetes v1.26 {#additional-changes} | ||
|
|
||
| On top of the described removals, this release will also include some additional changes to take into consideration: while not deprecations or removals, they introduce new features (or a new default behavior) through the graduation to Stable in this release; some of those changes are highlighted here. | ||
|
|
||
| ### Support for Windows privileged containers | ||
|
|
||
| Privileged container support allows containers to run with similar access to the host as processes that run on the host directly. Support for this feature in Windows nodes [will now graduate to stable](https://github.com/kubernetes/enhancements/issues/1981) and will be enabled by default. | ||
|
|
||
| ### CSI drivers migration | ||
|
|
||
| Following the GA of the [core CSI Migration](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/625-csi-migration) feature in the previous release, the effort continues and both the [vSphere](https://github.com/kubernetes/enhancements/issues/1491) and [Azure](https://github.com/kubernetes/enhancements/issues/1885) in-tree driver migration to CSI will be graduating to Stable. | ||
|
|
||
| ### Support of mixed protocols in Services | ||
|
|
||
| Currently, the API validation in Kubernetes that currently rejects Service definitions with different protocols if their type is LoadBalancer. In this release [support will be added that relaxes this validation](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/1435-mixed-protocol-lb). This feature depends on a strong interaction with the different cloud providers and for anyone planning to use it, a closer reading of the implications and risks is advised. | ||
|
|
||
| ## Looking ahead {#looking-ahead} | ||
|
|
||
| The official list of API removals planned for [Kubernetes 1.27](https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-27) currently includes: | ||
|
|
||
| * The beta CSIStorageCapacity (`storage.k8s.io/v1beta1`) | ||
|
|
||
| ### Want to know more? | ||
|
|
||
| Deprecations are announced in the Kubernetes release notes. You can see the announcements of pending deprecations in the release notes for: | ||
| * [Kubernetes 1.21](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.21.md#deprecation) | ||
| * [Kubernetes 1.22](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.22.md#deprecation) | ||
| * [Kubernetes 1.23](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.23.md#deprecation) | ||
| * [Kubernetes 1.24](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.24.md#deprecation) | ||
| * [Kubernetes 1.25](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.25.md#deprecation) | ||
| * We will formally announce the deprecations that come with [Kubernetes 1.26](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.24.md#deprecation) as part of the CHANGELOG for that release. | ||
|
|