Automated deployment CI/CD pipeline for Dotnet Web Apps: Using Azure Kubernetes Service

Automated deployments simplify the process of setting up a GitHub Action and creating an automated pipeline for your code releases to your Azure Kubernetes Service (AKS) cluster. Once connected, every new commit will kick off the pipeline, resulting in your application being updated.

This post will teach you how to use Azure services like Azure Kubernetes Service, and Azure Container Registry to establish a continuous integration and deployment (CI/CD) pipeline for a Dotnet web application.

Software development techniques and tools known as Continuous Integration and Continuous Deployment, or CI/CD, automate software development, testing, and deployment.

Software is delivered more quickly and reliably when the software development process is streamlined, releases are made faster, code quality is increased, and manual intervention is decreased thanks to CI/CD.

Common CI/CD tools and services include Jenkins, Travis CI, CircleCI, GitLab CI/CD, and other cloud-based CI/CD systems provided by AWS, Azure, and Google Cloud. In this post, we’ll use the GitHub Action service as one of those.

Prerequisites

• A GitHub account
• An AKS cluster
• An Azure Container Registry (ACR)
• An application to deploy

Configure an automated deployment — Click Here

Clean up resources

You can remove any related resources that you created when you don’t need them anymore individually or by deleting the resource group to which they belong. To delete your automated deployment, navigate to the automated deployment dashboard and select …, then select delete and confirm your action.

Originally published on Medium.