Solution architecture: Continuous integration and deployment (CI/CD) for containers with Visual Studio Team Services

Container deployment makes it easy to continuously update and improve your applications. Create replicable, manageable clusters of containers by orchestrating the continuous integration and deployment of those containers using Kubernetes or DC/OS in Azure Container Service. Use Visual Studio Team Services to deploy faster and more reliably by setting up a continuous build to produce and orchestrate your container images.

This solution is built on the Azure-managed services: Azure Container Service (AKS). These services run in a high-availability environment that is patched and supported, allowing you to focus on your solution instead of the environment they run in.

Continuous integration trigger Azure Container Service (Registry) Push container image Pull container image Continuous deployment trigger Deployment Visual Studio Team Services Git Visual Studio Team Services CI Application code, Docker files, Compose files, Deployment files Container images Compose files, Deployment files Environment specific Compose files, Deployment files Running containers Azure Container Service (Kubernetes, Swarm, or DC/OS) Visual Studio Team Services CD Commit

Implementation guidance

Products Documentation

Collaborate with your team members and share code for your container-ready applications in a Visual Studio Team Services Git repository.

Set up continuous-integration builds to create and test container images for every commit using Visual Studio Team Services Build. Push container images to Azure Container registry as part of your builds.

Set up a continuous-deployment pipeline through multiple environments (QA to Staging to Production) using Visual Studio Team Services Release Management. Integrate with various types of orchestrators in ACS.

Azure Container Service (AKS)

Use Azure Container Service and the different orchestrators it supports to deploy and manage your Container-based applications. Container images are stored in Azure Container Registry and pulled by the orchestrators (Kubernetes, DC/OS, Swarm etc.) running in Azure Container Service.

Related solution architectures