This article is a solution idea. If you'd like us to expand the content with more information, such as potential use cases, alternative services, implementation considerations, or pricing guidance, let us know by providing GitHub feedback.
Containers make it easy for you to continuously build and deploy your applications. By orchestrating deployment of those containers using Kubernetes in Azure Kubernetes Service (AKS), you can achieve replicable, manageable clusters of containers.
This document is about CI/CD for containers on Azure DevOps. If you are looking for solutions using github, see DevOps with AKS.
Potential use cases
By setting up a continuous build to produce your container images and orchestration, Azure DevOps increases the speed and reliability of your deployment.
Download a Visio file of this architecture.
- Change application source code.
- Commit Application Code.
- Continuous integration triggers application build, container image build and unit tests.
- Container image pushed to Azure Container Registry.
- Continuous deployment trigger orchestrates deployment of application artifacts with environment-specific parameters.
- Deployment to Azure Kubernetes Service (AKS).
- Container is launched using Container Image from Azure Container Registry.
- Application Insights collect and analyze health, performance, and usage data.
- Review health, performance, and usage information.
- Update backlog item.
- Container Registry: Store and manage container images across all types of Azure deployments
- Azure Kubernetes Service (AKS): Simplify the deployment, management, and operations of Kubernetes
- Application Insights: Detect, triage, and diagnose issues in your web apps and services
- Azure DevOps: Build and deploy multi-platform apps to get the most from Azure services