Kubernetes Removals and Deprecations In 1.24
Author: Mickey Boxell (Oracle)
As Kubernetes evolves, features and APIs are regularly revisited and removed. New features may offer an alternative or improved approach to solving existing problems, motivating the team to remove the old approach.
We want to make sure you are aware of the changes coming in the Kubernetes 1.24 release. The release will
deprecate several (beta) APIs in favor of stable versions of the same APIs. The major change coming
in the Kubernetes 1.24 release is the
.
This is discussed below and will be explored in more depth at release time. For an early look at the
changes coming in Kubernetes 1.24, take a look at the in-progress
It's safe to say that the removal receiving the most attention with the release of Kubernetes 1.24
is Dockershim. Dockershim was deprecated in v1.20. As noted in the :
"Docker support in the kubelet is now deprecated and will be removed in a future release. The kubelet
uses a module called "dockershim" which implements CRI support for Docker and it has seen maintenance
issues in the Kubernetes community." With the upcoming release of Kubernetes 1.24, the Dockershim will
finally be removed. In the article Don't Panic: Kubernetes and Docker,
the authors succinctly captured the change's impact and encouraged users to remain calm: Docker as an underlying runtime is being deprecated in favor of runtimes that use the
Container Runtime Interface (CRI) created for Kubernetes. Docker-produced images
will continue to work in your cluster with all runtimes, as they always have. Several guides have been created with helpful information about migrating from dockershim
to container runtimes that are directly compatible with Kubernetes. You can find them on the
Migrating from dockershim
page in the Kubernetes documentation. For more information about why Kubernetes is moving away from dockershim, check out the aptly
named: Kubernetes is Moving on From Dockershim
and the updated dockershim removal FAQ. Take a look at the Is Your Cluster Ready for v1.24? post to learn about how to ensure your cluster continues to work after upgrading from v1.23 to v1.24. Kubernetes contains a large number of components that evolve over time. In some cases, this
evolution results in APIs, flags, or entire features, being removed. To prevent users from facing
breaking changes, Kubernetes contributors adopted a feature deprecation policy.
This policy ensures 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 as indicated by the following stability levels: Removals follow the same deprecation policy regardless of whether an API is removed due to a beta feature
graduating to stable or because that API was not proven to be successful. Kubernetes will continue to make
sure migration options are documented whenever APIs are removed. Deprecated APIs are those that have been marked for removal in a future Kubernetes release. Removed
APIs are those that are no longer available for use in current, supported Kubernetes versions after having
been deprecated. These removals have been superseded by newer, stable/generally available (GA) APIs. As stated earlier, there are several guides about
Migrating from dockershim.
You can start with Finding what container runtime are on your nodes.
If your nodes are using dockershim, there are other possible Docker Engine dependencies such as
Pods or third-party tools executing Docker commands or private registries in the Docker configuration file. You can follow the
Check whether Dockershim deprecation affects you guide to review possible
Docker Engine dependencies. Before upgrading to v1.24, you decide to either remain using Docker Engine and
Migrate Docker Engine nodes from dockershim to cri-dockerd or migrate to a CRI-compatible runtime. Here's a guide to
change the container runtime on a node from Docker Engine to containerd. The The Kubernetes 1.25 and 1.26 releases planned for later this year will stop serving beta versions
of several currently stable Kubernetes APIs. The v1.25 release will also remove PodSecurityPolicy,
which was deprecated with Kubernetes 1.21 and will not graduate to stable. See PodSecurityPolicy
Deprecation: Past, Present, and Future for more information. The official list of API removals planned for Kubernetes 1.25 is: The official list of API removals planned for Kubernetes 1.26 is: Deprecations are announced in the Kubernetes release notes. You can see the announcements of pending deprecations in the release notes for: For information on the process of deprecation and removal, check out the official Kubernetes deprecation policy document.A note about Dockershim
The Kubernetes API removal and deprecation process
API removals, deprecations, and other changes for Kubernetes 1.24
What to do
Dockershim removal
kubectl convertkubectl convert plugin for kubectl
can be helpful to address migrating off deprecated APIs. The plugin facilitates the conversion of
manifests between different API versions, for example, from a deprecated to a non-deprecated API
version. More general information about the API migration process can be found in the Deprecated API Migration Guide.
Follow the
documentation to download and install the kubectl-convert binary.Looking ahead
Want to know more?