This document discusses using containers and Kubernetes in Azure to enable continuous integration and continuous deployment of applications. It describes setting up a continuous build pipeline in Visual Studio Team Services to automatically build container images, deploy them to Azure Container Registry, and orchestrate their deployment to Azure Container Service using Kubernetes. Application health and usage data is collected by Azure Application Insights.

1. Azure products used in this solution
© 2018 Microsoft. All rights reserved.
CI/CD for Containers
Change application source code.
Architecture overview
Containers make it easy for you to continuously build and deploy applications.
By orchestrating the deployment of those containers using Kubernetes in Azure
Container Service, you can achieve replicable, manageable clusters of containers.
By setting up a continuous build to produce your container images and
orchestration, Visual Studio Team Services increases the speed and reliability of
your deployment.
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 Container Service.
Container is launched using Container Image from Azure Container Registry.
Azure Application Insights collects and analyzes health, performance, and
usage data.
Review health, performance, and usage information.
Update backlog item.
1
2
3
4
5
6
7
8
9
10
Commit Application Code.
Visual Studio
Team Services Git
Visual Studio
Team Services CI
Visual Studio
Team Services CD
Azure Container Service
(Managed Kubernetes)
Azure Container
Registry
3 5
4
7
6
Engineer
Visual Studio Azure Application
Insights
1 9
8
Visual Studio
Team Services Backlog
2
10
Visual Studio
Application Insights
Azure Container Registry
Container Service
Visual Studio Team Services