Microsoft will cease supporting its Azure Container Service (ACS) as of January 31, 2020[1], officials revealed last week. ACS is being replaced by Microsoft's Azure Kubernetes Services (AKS), which the company introduced in 2017.
Also: Best Green Monday 2018 deals: Business Bargain Hunter's top picks[2]
Microsoft's ACS for developing, deploying and maintaining containers has supported Kubernetes -- an open-source container-orchestration standard -- since early 2017.
Because of Kubernetes' success, Microsoft added a dedicated Kubernetes container service, AKS[3], in the Fall of 2017. At the time Microsoft introduced AKS, officials said they planned to continue to offer ACS, originally introduced in 2015[4]. In March 2018, however, Microsoft officials said they would be deprecating ACS at some point[5], but didn't provide a specific date.
On December 5, Microsoft officials said in a blog post that ACS will no longer be supported as of January 31, 2020. Beginning on that date, all ACS application programming interfaces (APIs) will be blocked. Users will no longer be able to create new clusters, or update or scale existing clusters. They will be able to list and delete existing clusters.
Also: What Kubernetes really is, and how orchestration redefines the data center[6]
Microsoft's recommendations for existing ACS users[7] are to migrate to AKS or the ask-engine open-source project if they use Kubernetes. If they use ACS with Docker, Microsoft suggests moving to the Basic or Standard/Advanced Docker Enterprise Edition for Azure solution template. If they use ACS with DC/OS, the company is advocating users move to the Mesosphere DC/OS Enterprise or Mesosphere DC/OS Open Source solution template.
Must read
Last week, Microsoft made