Closed colemickens closed 6 years ago
Very interested in feedback here, as we have spent considerable effort and brainpower toward making ACS work for our deployments.
"continue to support" doesn't feel like a particularly strong commitment to ACS.
I am also interested in this. I posted this question in #sig-azure a few days ago and didn't get a huge response from the dev team.
Answers inline-
Will ACS and AKS continue to co-exist? Yes for the time being. ACS is a GA service while AKS is a preview service. When they reach parity we will revisit this topic.
Is ACS deprecated? If so, does this mean generally DC/OS and Swarm are going to be deprecated in Azure (other than where supported directly by Mesosphere and Docker Inc). ACS is not deprecated. We are looking at making DC/OS and Swarm available only through the Azure marketplace where they have always been available.
Do enhancements to ACS-Engine directly flow to AKS, or no? It seems (per a Twitter thread?) that AKS is still missing some things enabled in ACS-Engine - its unclear if it's just not wired up or if AKS is a separate code effort entirely. A decision on this has not been made yet.
@colemickens Let me know if you need further clarification.
I attended a workshop in MS, they explained that Kubernetes is winning among all other orchestrators, why AKS will also become the winner as a perfect implementation of managed Kubernetes in Azure. I think that will explain everything.
(As this is a meta question, neither a feature request nor issue, I'm forgoing the template...)
There were some questions about this in
#sig-azure
and I had my own questions as I was kicking the tires today. In general, I'm hoping that the ACS/AKS team(s) can document the answers to these questions and/or generally highlight the expected roadmaps for ACS and AKS.Questions: