documents VS website

It's not about terraform handling it or not, it's about ensuring that drift is automatically corrected without a CI trigger. One of the core principles of GitOps is continuous reconciliation. This requires a reconciliation loop, e.g. some task that runs automatically and without user intervention. As far as I can tell from their docs Digger only runs its steps on a pull request, similar to Atlantis (but "without the backend"). This is continuous delivery, but it's not continuous reconciliation, and therefore not GitOps. GitOps would be something like combining Flux or ArgoCD with Crossplane.

think i'm going to take the feedback from this discussion to the opengitops working group tomorrow, hoping we can maybe get it defined in their vendor agnostic gitops glossary https://github.com/open-gitops/documents/blob/main/GLOSSARY.md haha, which i'm sure chatgpt will figure out about like 12 seconds later, consider correct, and then just wire the architecture together for us. but we can just start with kubefirst while chatgpt is trying to catch up haha.

The GitOps term was coined back in 2017 by Weaveworks, and paraphrasing OpenGitOps, a GitOps system is based on the following principles:

That's why there's systems for continuous reconciliation. I'ts one of the four fundamental principles of GitOps.

https://opengitops.dev/ https://github.com/open-gitops/documents

(Here is a link: https://github.com/open-gitops/documents/pull/51)

In 2021, the first OpenGitOps Standard v1 was created, to make sure we all GitOps enthusiasts speak the same language. For more information go to opengitops.dev.

The working group has been hard at work, over many meetings, github discussions, revisions, blood, sweat, and tears we've just merged the pre-release GitOps Principles and glossary. Check them out here and be sure to make issues/comments. It'd be great to hear everyone's thoughts.

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