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 items that have been deprecated or removed in CloudOps for Kubernetes releases.

Deprecations

Alert Logic daemonset install is deprecated

The optional installation and deployment of the Alert Logic daemonset, which is controlled by the parameter TF_VAR_al_registration_key in the CloudOps for Kubernetes docker-compose.yml file, is deprecated as of CloudOps for Kubernetes release 2.14 and will be removed in a future release.

The create-or-delete-mysql-server job will be removed in a future release

The Jenkins job create-or-delete-mysql-server is deprecated as of Cloudops For Kubernetes release 2.13, and will be removed in an upcoming release of CloudOps for Kubernetes. You should begin using the replacement job create-and-manage-database-server instead. The new create-and-manage-database-server job will detect and use Terraform worksaces created by the create-or-delete-mysql-server job. Use the new create-and-manage-database-server job to manage Amazon Aurora MySQL database services that you previously created with the create-or-delete-mysql-server. Use the new create-and-manage-database-server job to create new Amazon Aurora MySQL or Amazon Postgres RDS database services.

Support for root user containers will be removed in a future release

Support for the root user containers built by older releases of the docker Git repository are deprecated as of Cloudops For Kubernetes release 2.13. Support for deploying root user container images will be removed in an upcoming release of CloudOps for Kubernetes. You should update to release 4.2.x or newer of the Elastic Path docker Git repository. See Update Containers to Run as Non-root for more information.

Account Management API deployment will be removed in a future release

The Self Managed Commerce Account Management API is the older Account Management offering that could be deployed separately beside Self Managed Commerce. As mentioned in the Account Management API documentation, it has been deprecated in favour of newer Account Management functionality built into Self Managed Commerce 8.2 and later. Support for deploying or updating the Account Management API will be removed from CloudOps for Kubernetes in an upcoming release.

The create-additional-kubernetes-cluster job will be removed in a future release

The Jenkins job create-additional-kubernetes-cluster and the ability to create and manage additional EKS clusters through Jenkins are deprecated and will be removed in a future release. Elastic Path is not aware that this feature is used and will remove it to simplify the CloudOps for Kubernetes design and implementation.

Removals

The dockerd runtime was removed in the earlier release 2.13

Support for the dockerd container runtime was deprecated in CloudOps for Kubernetes release 2.12 and removed in release 2.13. CloudOps for Kubernetes has switched to the containerd runtime as-of release 2.13. This change has 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.

CloudOps for Kubernetes release 2.13 is based on EKS 1.24 and so must also move from the dockerd runtime to the containerd runtime.

note

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

Considerations

There is no impact on the jobs, services or deployments included in and provided as part of CloudOps for Kubernetes. All functionalities provided as part of CloudOps for Kubernetes work transparently with the new containerd runtime. However, it is possible that you have added tools that rely on the dockerd runtime to your CloudOps for Kubernetes cluster. 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.