CI/CD Pipelines with AKS and Azure DevOps - Tutorial

Implementing CI/CD (Continuous Integration/Continuous Deployment) pipelines with Azure Kubernetes Service (AKS) and Azure DevOps allows you to automate the build, test, and deployment processes of your applications in AKS. With CI/CD pipelines, you can ensure faster, more reliable, and consistent software delivery. This tutorial will guide you through the steps to set up CI/CD pipelines with AKS and Azure DevOps.


Before you begin, ensure you have the following prerequisites:

  • An Azure subscription
  • An AKS cluster deployed
  • An Azure DevOps organization
  • A Git repository for your application code

Step 1: Set Up Azure DevOps Pipeline

To create a CI/CD pipeline with AKS and Azure DevOps, follow these steps:

  1. Create an Azure DevOps pipeline and connect it to your Git repository:

      - main

vmImage: 'ubuntu-latest'


script: |
echo "Building and testing the application..."

Add your build and test commands here

displayName: 'Build and Test'

task: KubernetesManifest@0
action: 'deploy'
kubernetesServiceConnection: ''
manifests: '**/*.yaml'
displayName: 'Deploy to AKS'

In the above example, replace '' with the name of your AKS service connection in Azure DevOps.

Step 2: Configure AKS Service Connection

Next, configure a service connection in Azure DevOps to connect to your AKS cluster:

  1. In Azure DevOps, go to your project's settings and select 'Service Connections'.
  2. Create a new 'Kubernetes' service connection.
  3. Provide the necessary details, such as the AKS cluster name, resource group, and authentication method.
  4. Test the connection to ensure it is set up correctly.

Step 3: Run the Pipeline

Once the pipeline is set up and the AKS service connection is configured, you can run the pipeline to build, test, and deploy your application to AKS:

  1. Commit and push your application code to the Git repository connected to the Azure DevOps pipeline.
  2. In Azure DevOps, navigate to the pipeline and click 'Run Pipeline'.
  3. Monitor the pipeline execution and verify the successful deployment of your application to AKS.

Common Mistakes to Avoid

  • Incorrectly configuring the AKS service connection in Azure DevOps.
  • Not properly defining the build and deployment steps in the pipeline configuration.
  • Forgetting to commit and push the application code to the Git repository before running the pipeline.

Frequently Asked Questions

  1. Can I use multiple stages in my CI/CD pipeline?

    Yes, you can define multiple stages in your Azure DevOps pipeline to represent different environments, such as development, testing, and production.

  2. Can I add tests to my CI/CD pipeline?

    Yes, you can include automated tests in your CI/CD pipeline to ensure the quality of your application before deployment.

  3. Can I use Azure DevOps to deploy container images to AKS?

    Yes, you can build and push container images to a container registry using Azure DevOps, and then deploy those images to AKS.

  4. Can I trigger the pipeline automatically on code changes?

    Yes, you can configure triggers in your Azure DevOps pipeline to automatically start the pipeline when changes are pushed to the Git repository, such as on branch updates or pull requests.

  5. Can I integrate other tools or services with my CI/CD pipeline?

    Yes, Azure DevOps provides integrations with various tools and services, allowing you to customize and extend your CI/CD pipeline to fit your specific requirements.


Implementing CI/CD pipelines with Azure Kubernetes Service (AKS) and Azure DevOps streamlines the software delivery process, enabling faster and more reliable deployments. By setting up an Azure DevOps pipeline, configuring the AKS service connection, and running the pipeline, you can automate the build, test, and deployment of your applications to AKS. Avoid common mistakes such as misconfiguring the AKS service connection or missing proper pipeline configuration. With CI/CD pipelines, you can enhance your development workflow, ensure consistent deployments, and accelerate time-to-market for your applications running on AKS.