Container CI/CD using Jenkins and Kubernetes on Azure Kubernetes Service (AKS)

Containers make it easy for you to continuously build and deploy applications. By orchestrating the deployment of those containers using Azure Kubernetes Service (AKS), you can achieve replicable, manageable clusters of containers.

By setting up a continuous build to produce your container images and orchestration, you can increase the speed and reliability of your deployment.

Déploiement continu et intégration continue de conteneurs à l’aide de Jenkins et Kubernetes sur Azure Kubernetes Service (AKS)Les conteneurs vous permettent de facilement générer et déployer des applications en continu. En orchestrant le déploiement de ces conteneurs à l’aide d’Azure Kubernetes Service (AKS), vous pouvez obtenir des clusters de conteneurs gérables et réplicables.123456778

Change application source code.

Commit code to GitHub.

Continuous Integration Trigger to Jenkins.

Jenkins triggers a build job using Azure Kubernetes Service (AKS) for a dynamic build agent.

Jenkins builds and pushes Docker container to Azure Container Registry.

Jenkins deploys your new containerised app to Kubernetes on Azure.

Container Service (AKS), backed by Azure Cosmos DB.

Grafana displays visualisation of infrastructure and application metrics via Azure Monitor.

Monitor application and make improvements.

  1. 1 Change application source code.
  2. 2 Commit code to GitHub.
  3. 3 Continuous Integration Trigger to Jenkins.
  4. 4 Jenkins triggers a build job using Azure Kubernetes Service (AKS) for a dynamic build agent.
  5. 5 Jenkins builds and pushes Docker container to Azure Container Registry.
  1. 6 Jenkins deploys your new containerised app to Kubernetes on Azure.
  2. 7 Container Service (AKS), backed by Azure Cosmos DB.
  3. 8 Grafana displays visualisation of infrastructure and application metrics via Azure Monitor.
  4. 9 Monitor application and make improvements.

Implementation guidance

Related solution architectures