Azure CI/CD Pipeline using Azure Pipelines and Argo CD | Multi Microservice

Continuous integration (CI) is the practice of automating the integration of code changes from multiple contributors into a single software project.

Continuous delivery (or) deployment (CD) is a 2 part process that refers to the integration, testing, and delivery of code changes. Continuous delivery stops short of automatic production deployment, while continuous deployment automatically releases the updates into the production environment.

First Part 👉 “GitHub to Azure DevOps Migration | Azure Pipelines”

The stage environment is as similar to the production environment as it can be. You’ll have all of the code on a server this time instead of a local machine. It’ll connect to as many services as it can without touching the production environment.

buymeacoffee ☕ 👈 Click the link

All of the hard core testing happens here. Any database migrations will be tested here and so will any configuration changes. When you have to do major version updates, the stage environment helps you find and fix any issues that come up too.

Azure Repos is a set of version control tools that you can use to manage your code. Whether your software project is large or small, using version control as soon as possible is a good idea.

Built as part of the CI process, It’s an effective DevOps pipeline enables companies to rapidly develop, test, and deploy new code on an ongoing basis.

Push build the new image in private Azure container registry, and push it to your registry.

updateK8sManifests.sh → Update the Azure repo what changes made using by shell script.

Argo CD is an open-source GitOps continuous delivery tool. It monitors your cluster and your declaratively-defined infrastructure stored in a Git repository and resolves differences between the two effectively…