To further make the adoption and use of Kubernetes easier, Microsoft will now allow developers to reuse their existing Azure Kubernetes Service (AKS) cluster in Azure DevOps Projects.
The adoption of Kubernetes is rapidly growing among large enterprises. According to a survey by The New Stack, Kubernetes is the most widely used orchestration platform, having adopted by 69% of enterprises.
Microsoft provides AKS and Azure DevOps Projects solutions to help customers adopt Kubernetes. The Azure Kubernetes Service is a full managed Kubernetes container orchestration service that simplifies the deployment and operations of Kubernetes and allows customers to scale their application infrastructure.
Whereas, the Azure DevOps Projects helps customers to easily launch container apps on any Azure Service. It comes with a git code repository, Application Insights Integration, and a continuous delivery (CD) pipeline setup to deploy apps to Azure.
For instance, it can be used for provisioning AKS and Azure Container Registry, and build and deploy container apps to AKS using Azure Pipelines. Further, the customers can monitor their code commits, builds, and deployments from DevOps Projects dashboard in Azure portal.
However, the customers who use Azure DevOps Projects to deploy their apps to AKS, needed to create a new AKS cluster every time they deploy an app.
Microsoft has taken that into consideration and announced that customers will now be able use Azure DevOps Projects for deploying multiple apps to a single AKS cluster. The new feature is now generally available in the Azure Portal.
Also read: Azure IoT Edge now supports virtual machines
“Kubernetes is going from strength to strength as adoption across the industry continues to grow. But there are still plenty of customers coming to container orchestration for the first time while also building up their familiarity with Docker and containers in general,” wrote, Atul Malaviya, Principal Program Manager, Azure DevOps, in a blog post.
“We see the need to help teams go from a container image, or just a git repo, and help get them to an app running in Kubernetes in as few steps as possible. It’s also important that we do this in a way that will allow them to customize afterward and build on their knowledge as they go.”