Previously it was always a struggle to setup your Kubernetes Cluster with the GitOps approach leading to teams manually deploying manifests and helm charts which results in Kubernetes clusters that are hard to maintain. As of today git is still the most popular solution for managing your Kubernetes Cluster with IaC.

The GitOps template uses the ArgoCD's App of Apps model and all packages (including ArgoCD itself) will receive automatic update suggestions via pull requests thanks to the Renovate and Glasskube integration.

In order to get started, you just need to create your own repository from our template and bootstrap it with a single command. This will include: - ArgoCD for GitOps - Kube-Prometheus-Stack for Monitoring - Postgres Operator (Cloud Native PG) - Glasskube for package management - Renovate for updates via pull request

Additionally, we deployed Shiori (https://github.com/go-shiori/shiori) as a simple application that requires a Postgres database. This is meant as an example application you can replace with your application you want to deploy to Kubernetes.

I also created a walk-through demo video explaining the setup steps in more detail: https://www.youtube.com/watch?v=Xbs2Tq-dgbI

Sometimes, you may need to manually refresh the App of Apps inside ArgoCD to ensure that the other apps appear in the cluster.

In addition, we will work on the following features in the future: - Support private repositories from the beginning. At the moment the repository needs to be public during bootstrapping. The visibility can be marked as private afterwards. (You will also need to manually configure your personal access token in ArgoCD) - Improve the Renovate integration, so we don’t need the custom regex matcher and can upgrade the glasskube manifest.

Feel free to comment what is still missing or what you would do differently?