k8s-gitops VS website

Check it out here on Github.

My entire Kubernetes cluster state is declaratively defined as code in my GitOps repository - feel free to check it out here https://github.com/xUnholy/k8s-gitops

Yep! Using Fluxv2 to leverage GitOps - https://github.com/xUnholy/k8s-gitops

Also - this is pretty awesome: https://raspbernetes.github.io/ My currently running RPi4 home lab cluster was built using this.

Pushing out multi-cluster topology with GitOps using fluxv2. I run this cluster purely on Raspberry Pi's https://github.com/xUnholy/k8s-gitops

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