Why is Microsoft retiring Azure Container Service? Well, all the capabilities of ACS for Kubernetes are available with AKS. Hence, the tech giant decided to retire ACS as a standalone service.

Users wouldn’t be able to create new clusters, update, or scale existing clusters using the portal, CLI, or Resource Manager templates.

However, Microsoft will allow listing and deletion of existing clusters using client tools. The existing clusters and applications will continue to work but Microsoft wouldn’t support ongoing operation of these clusters.

“Please note that ongoing operation of these clusters is your responsibility and is not within Azure’s support scope,” wrote Microsoft in a blog post.

Further, Microsoft will also stop development of acs-engine project which is used to create unmanaged container orchestrator cluster. The tech giant is migrating the Kubernetes part of acs-engine project to aks-engine repo.

Before the Azure Container Service retires on January 31, 2020, the users of Kubernetes orchestrator will need to migrate to AKS before ACS retires. The migration will prove to be beneficial for users as it will come with feature enhancements.

These enhancements include simplified deployment of managed Kubernetes clusters in Azure, reduced complexity and operational overhead of managing Kubernetes, as well as handling of critical tasks like health monitoring and maintenance.

Whereas, the users of ACS with Docker will need to switch to the Basic or Standard Docker Enterprise Edition for Azure solution template. For users of ACS with DC/OS, Microsoft recommends migration to Mesosphere DC/OS Enterprise or Mesosphere DC/OS Open Source solution template.

Categories

Categories

Get the latest information related to what’s trending in the web hosting, domain, data center and reseller industry. A one-stop destination for IT news, CXOs’ interviews, articles and infographics for web hosting providers and IT professionals.