Deprecations and Removals · CloudOps for Kubernetes

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.

Contact Us

Contact Elastic Path Support, or your Elastic Path Customer Success Manager, if any planned deprecations or removals will negatively impact you and your team.

Removals

The `create-additional-kubernetes-cluster` job cannot be added

The ability to enable the create-additional-kubernetes-cluster Jenkins job is removed in CloudOps for Kubernetes release 3.1, though customers who previously enabled the job can continue to use the job in CloudOps for Kubernetes release 3.1. Contact Elastic Path Support, or your Elastic Path Customer Success Manager, if you rely on this job.

The `create-or-delete-mysql-server` job has been removed

The create-or-delete-mysql-server Jenkins job is removed in CloudOps for Kubernetes release 3.1. Use the create-and-manage-database-server job to manage Amazon Aurora MySQL database services that you previously created with create-or-delete-mysql-server. The create-and-manage-database-server job will detect and use Terraform workspaces created by the create-or-delete-mysql-server job. To continue managing Amazon Aurora MySQL database services, run the create-and-manage-database-server job with the same kubernetesNickname value and correct databaseType and database engine version values.

Account Management API deployment has been removed

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 has been removed from CloudOps for Kubernetes in release 3.1.

Deprecations

MySQL 5.7 support will be removed in a future release

MySQL 5.7 support is deprecated as of Cloudops for Kubernetes release 3.2, and will be removed in a future release. Oracle ended standard support for MySQL 5.7 in October 2023, and AWS will end standard support for MySQL 5.7 Aurora instances in October 2024.

When support for MySQL 5.7 is removed from CloudOps for Kubernetes, support for both containerized MySQL 5.7 and for Amazon RDS Aurora MySQL 5.7 will be removed.

CloudOps for Kubernetes users who are on MySQL 5.7 are encouraged to migrate to MySQL 8.0 or PostgreSQL 14. The Self-Managed Commerce application development team has shared related information at Migrating off of MySQL 5.7.

For information about database server options in CloudOps for Kubernetes, see Database Server Options.

Alert Logic daemonset will be removed in a future release

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 the next release, CloudOps for Kubernetes 3.1.

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 the next release, CloudOps for Kubernetes 3.2. Elastic Path is not aware that this feature is used and will remove it to simplify the CloudOps for Kubernetes design and implementation.

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 the next release. 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.

Additional Jenkins plugins will be removed in a future release

Additional plugins that have been manually installed will be removed during the Jenkins deployment process in the next release, CloudOps for Kubernetes 3.3. This change will affect all future versions of CloudOps for Kubernetes. In order to continue using Jenkins plugins that are not defined in CloudOps for Kubernetes, they should be added to the Jenkins Helm chart under the additionalPlugins section. See Customizing Jenkins for more information.