Container CI/CD using Jenkins and Kubernetes on Azure Kubernetes Service (AKS)
If you'd like to see us expand this article with more information (implementation details, pricing guidance, code examples, etc), let us know with GitHub Feedback!
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.
Download an SVG of this architecture.
- 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 containerized app to Kubernetes on Azure.
- Container Service (AKS), backed by Azure Cosmos DB.
- Grafana displays visualization of infrastructure and application metrics via Azure Monitor.
- Monitor application and make improvements.
- Azure Kubernetes Service (AKS): Simplify the deployment, management, and operations of Kubernetes.
- Container Registry: Store and manage container images across all types of Azure deployments.
- Azure Cosmos DB: Globally distributed, multi-model database for any scale.
- Azure Monitor: Highly granular and real-time monitoring data for any Azure resource.
- Visual Studio Code: Build and deploy multi-platform apps to get the most from Azure services.
- Integrating Jenkins with Azure Container Service and Kubernetes
- Pushing Docker images to Azure Container Registry
- Connect existing Node.js to Cosmos DB using the MongoDB connector
- Monitor your Azure services using Grafana
- Get the Azure Extension Pack for Visual Studio Code