Posted on Sep 25 Our team has dug into some of the basics of GitOps over the past week. So far, we've talked about:1) Declarative2) Versioned and Immutable3) Pulled Automatically4) Continuously ReconciledGitOps tools boil down to:A Git repositoryAn artifact repository (by default, a branch in the Git repo)An agent that is responsible for ensuring that the state of the cluster matches the configuration defined in the artifact repository (over time)Applying these principles to the use of the tools identified, we can effectively manage our Kubernetes clusters and workloads therein with auditable, automated changes and maintain a consistent configuration despite unintentional configuration drift.Now, it's time to dig in to the next GitOps tool in the GitOps ecosystem - Argo CD.Argo CD is part of the Argo ecosystem of tools. Argo CD is a GitOps engine and continuous delivery tool. Argo CD is a Kubernetes controller that monitors the applications running inside your cluster and ensures that it matches the desired state (as represented by manifests or Helm charts in your target repository).The Azure Marketplace is integrated into our Azure Kubernetes Service (AKS) clusters and provides a way for open source and commercial offerings that are container-based to be easily deployed into AKS clusters.Argo CD is offered through the Azure Marketplace. Marketplace offers are installed as extensions into AKS.We'll start in the Azure Portal on the AKS Cluster view.We'll navigate down the left-hand side of the page to the Extensions + applications item under Settings.Next, we'll select Add.We'll put argocd in the search box and select the Argo CD packaged by Bitnami offering. The search will return two options, one a container and one a Kubernetes App. We'll select the Kubernetes App and click CreateThis will open up the Create Argo CD packaged by Bitnami page. We specify a subscription and resource group, as well as whether or not we need a new AKS cluster.The next step will be moving to the Kubernetes Cluster (AKS) Details tab.After we specified the cluster details, we move to the Application Details tab. Here, we add a resource name (which has to be lowercase letters or numbers - no symbols - of between 6 and 30 characters). We can customize the namespace, but we'll take the default. And we can decide if we want the extension to be able to automatically deploy minor version updates.The last step of this process is to go to the Review + create tab. Here we'll see the versions of the application and deployment resources, as well as any potential cost (for the packaged application specifically) and other details like terms of use. We'll click Create here.Clicking Create kicks of the deployment process.After the deployment completes, we'll have argocd listed in our Extension + applications section of our AKS Cluster.We'll retrieve the Argo CD Server password with kubectl.(or if you are like me and using PowerShell)Then, we need to expose the Argo CD server so we can access it from our workstation.Then, we can access the Argo CD Server at https://localhost:30443 with the user name admin and the password we retrieved in the previous step.From there, we could jump into the sample in the Argo CD documentation and carry on from there.The AKS Marketplace provides a convenient way to installed a somewhat managed experience and quickly get started with new applications.Getting Argo CD up and running is pretty simple and we can start exploring it in greater depth in our AKS environment.Leave your questions in the comments or come over to the Microsoft Open Source Discord and chat with me and my team in the cloud-native channel!And check back with our team tomorrow, as Paul digs into Flagger.Templates let you quickly answer FAQs or store snippets for re-use. Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink. Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Omar Hiari - Sep 15 Avelyn Hyunjeong Choi - Sep 15 Scofield Idehen - Sep 5 Emmanuel Ugwu - Sep 5 Any language. Any platform. Once suspended, azure will not be able to comment or publish posts until their suspension is removed. Once unsuspended, azure will be able to comment and publish posts again. Once unpublished, all posts by azure will become hidden and only accessible to themselves. If azure is not suspended, they can still re-publish their posts from their dashboard. Note: Once unpublished, this post will become invisible to the public and only accessible to Steven Murawski. They can still re-publish the post if they are not suspended. Thanks for keeping DEV Community safe. Here is what you can do to flag azure: azure consistently posts content that violates DEV Community's code of conduct because it is harassing, offensive or spammy. Unflagging azure will restore default visibility to their posts. DEV Community — A constructive and inclusive social network for software developers. With you every step of your journey. Built on Forem — the open source software that powers DEV and other inclusive communities.Made with love and Ruby on Rails. DEV Community © 2016 - 2023. We're a place where coders share, stay up-to-date and grow their careers.