website VS aks-store-demo

OpenGitOps group has defined 5 principles, and while I won't delve into them, here, you can read more. If you take a look at those principles you will see that they are, in some sense related to some Kubernetes concepts.

What is OpenGitOps?

The OpenGitOps standards group defines GitOps using a set of four principles:

On top of Talos, I'm running a Kubernetes cluster with everything deployed using GitOps principles. GitOps is a development methodology that uses Git as the single source of truth for infrastructure and application deployments. It's a great way to manage infrastructure changes, and it means that I can easily roll back any changes if something goes wrong.

opengitops.dev is the GitOps working group created by Amazon, GitHub and even Weaveworks which coined the "GitOps" term in their 2017 blog post.

Having "GitOps" on its own doesn't sound right when I say it. Based on the OpenGitOps Principles, we are architecting the GitOps Agent in this discussion, so I'd include that too.

GitOps principles differ from the traditional CI & CD pipeline approach. In the last few years, the GitOps working group under CNCF formalized all the ideas developed around GitOps into a cohesive set of principles that have become the GitOps Principles.

There are four principles of GitOps, and according to Open GitOps, they are:

The Gitops definition

The dev-app Kustomization deploys the GitRepository resource which points to the flux-k8s-ext branch in my AKS Store Demo Manifests repo, and Kustomization resource to deploy the AKS Store Demo application

We'll move really fast through the AKS cluster provisioning, bootstrapping process, and deploying the AKS Store Demo sample app.

# navigate to the home directory or wherever you want to clone the repo cd ~ # fork and clone the repo to your local machine gh repo fork https://github.com/azure-samples/aks-store-demo.git --clone # make sure you are in the aks-store-demo directory cd aks-store-demo # since we are in a forked repo, we need to set the default to be our fork gh repo set-default

We'll deploy my new favorite demo app, AKS Store Demo to our AKS cluster and then make some changes to the application and see how FluxCD handles them.

> git clone https://github.com/smurawski/aks-store-demo > cd aks-store-demo > git checkout origin/helm > git checkout -b helm > git remote add upstream https://github.com/Azure-Samples/aks-store-demo > git fetch upstream > git rebase upstream/main Successfully rebased and updated refs/heads/helm.