website VS argocd-autopilot

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?

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.

Just to clarify, there is no "Push" GitOps; this would go against one of the core principles that define GitOps (pulled automatically), see https://opengitops.dev/.

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.

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

GitOps simply says that your single source of truth should be source control. Check https://opengitops.dev/. In theory you can follow GitOps with just SVN + Concourse CI + EC2 + your custom code.

See https://opengitops.dev/ for the full story and especially the two-way-sync (principle 4)

I use Argo CD Autopilot which bootstraps Argo CD in a self-managing structure. If nothing else, copy the repo structure https://github.com/argoproj-labs/argocd-autopilot

Argo CD Autopilot is under active development. You are welcome to participate in Github as well as the #argo-cd-autopilot channel in the CNCF slack.

We use the same approach internally and we fully open-sourced our solution at https://argocd-autopilot.readthedocs.io/en/stable/

I recommend utilising Autopilot a companion project that not only installs Argo CD but also commits all configurations to git so Argo CD can maintain itself using GitOps.

Check https://argocd-autopilot.readthedocs.io/en/stable/ It is an installer that does exactly that. It installs ArgoCD, sets it up to manage itself and offers a suggested bootstrap for your applications

Checkout the ArgoCD autopilot if you're using kustomize rather than helm

If you like this approach, checkout argo autopilot