In the previous post in this series I talked about Azure Arc and it’s multiple flavors. Although one Azure managed control plane for all your resources no matter if there are on premise, on Azure or hosted at another cloud provider sounds great if you are an IT ops guy(or girl) but why should you care as a developer as well?
It is important to understand that the Azure Arc story has 2 dimensions.
1. Arc enabled infrastructure
The first dimension is the Arc enabled infrastructure. This is the part that I already talked about and that allows you to connect and control hybrid resources like they are native Azure resources. This allows you to use additional Azure Services like Azure Policy, Azure Monitor, and so on to govern, secure and monitor these services.
2. Arc enabled services
The second dimension is Arc enabled services. Once you have an Arc enabled infrastructure, you can start to deploy and run Azure Services outside Azure while still operation them from Azure. This allows you to run Azure Services like App Services, Functions, Logic Apps, API Management and Event Grid outside Azure!
How does this work?
Azure application services with Azure Arc is available as an extension on Azure Arc-enabled Kubernetes clusters that allow you to easily install the App Service control plane on Kubernetes and start deploying your applications to it. So in our next posts, we’ll focus on how to Arc-enable your Kubernetes cluster and get the Azure Application services cluster extension up and running.