Azure Container Service Will Retire on January 31, 2020
Published date: December 05, 2018
In 2017, we introduced Azure Kubernetes Service (AKS) for simplifying Kubernetes management, deployment, and operations. Because it fully replaces Azure Container Service (ACS) capabilities for Kubernetes, ACS will be retired as a standalone service on January 31, 2020.
If you use the Kubernetes orchestrator, please migrate to AKS by January 31, 2020. We encourage you to make the switch sooner to take advantage of these feature enhancements:
· Simplified deployment of managed Kubernetes clusters in Azure.
· Reduced complexity and operational overhead of managing Kubernetes.
· Critical tasks like health monitoring and maintenance are handled by AKS.
If you use ACS with Docker or DC/OS, please migrate to a solution template as recommended below.
How this will affect you
Beginning January 31, 2020, all ACS APIs will be blocked. Additionally, you’ll no longer be able to create new clusters, update, or scale existing clusters using the portal, CLI, or Resource Manager templates. However, you’ll still be able to list and delete existing clusters using these client tools. While the existing clusters and the applications running on them should continue to work after January 31, 2020, there will be no technical support available or feature improvements.
The acs-engine project used for creating unmanaged container orchestrator clusters has also been deprecated and will no longer see active development. Instead, we have migrated the Kubernetes portion of that project to a new repo, aks-engine and will continue the open-source work backing Kubernetes on Azure there. As with ACS, existing clusters deployed via acs-engine should continue to run and aks-engine will offer backward compatibility for scale and upgrade operations. For new clusters, we encourage you to move to using aks-engine.
Migrate from ACS to one of the following options no later than January 31, 2020:
Still have questions? Contact us.