Deprecations and Removals

Overview

Elastic Path will occasionally decide to remove features and capabilities from CloudOps for Kubernetes. This page is where we will announce our plans for deprecating or removing such features.

The Docker Runtime Will be Removed in Release 2.13

Support for the dockerd container runtime is deprecated in CloudOps for Kubernetes release 2.12 and will be removed in release 2.13. CloudOps for Kubernetes will switch to the containerd runtime in release 2.13. This change will have no impact on the functionality of CloudOps for Kubernetes or containerized services.

Background

Amazon Elastic Kubernetes Service (EKS) requires that all EKS clusters using the dockerd container runtime switch to the containerd runtime engine in EKS version 1.24. The Kubernetes open source project has removed support for the dockerd runtime in Kubernetes version 1.24. For more information, see Amazon EKS is ending support for Dockershim.

To prepare for this, CloudOps for Kubernetes release 2.13 will remove dockerd as the default runtime and use containerd instead.

note

This change will only impact the Kubernetes cluster and containers running in the Kubernetes cluster. You will still be able to use Docker on local development workstations, on your Operations Workstation, and elsewhwere. You will still be able to use Docker outside of Kubernetes to run container images built using CloudOps for Kubernetes.

Preparation

It is important to review any additional in-cluster tools you may have to see if any rely on dockerd being present. If there are any, you must investigate options to upgrade them in preparation for the upcoming switch to containerd.

There will be no impact on any of the jobs, services or deployments included in and provided as part of CloudOps for Kubernetes. All functionalities provided as part of CloudOps for Kubernetes will work transparently with the new containerd runtime. However, it is possible that you might have added tools that rely on the dockerd runtime. Review any third-party or custom tools that integrate with the Kubernetes cluster to determine if they will be impacted by this upcoming change. For more information, see the Kubernetes page Check whether dockershim removal affects you.