aks-store-demo-manifests VS website

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

The great thing about Flux is that it can be bootstrapped using GitOps. So we'll point to a branch in my AKS Store Demo Manifests repo which has everything we need to get the cluster setup quickly.

# navigate to the home directory or wherever you want to clone the repo cd ~ # login to GitHub gh auth login --scopes repo,workflow # fork and clone the repo to your local machine gh repo fork https://github.com/pauldotyu/aks-store-demo-manifests.git --clone # make sure you are in the aks-store-demo-manifests directory cd aks-store-demo-manifests # since we are in a forked repo, we need to set the default to be our fork gh repo set-default # merge the "kustomize" branch into "main" git merge origin/kustomize # push the change up to your fork git push # set the repo url export GITHUB_REPO_URL=$(gh repo view --json url | jq .url -r) # set your GitHub username export GITHUB_USER= # set your GitHub personal access token export GITHUB_TOKEN=

gh repo fork https://github.com/pauldotyu/aks-store-demo-manifests.git --clone # change into the repo directory cd aks-store-demo-manifests

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