bootstrap-repo VS documents

So why am I telling you all this? Because this is how I point Kubernetes ingresses at apps which live outside the clusters. It's not entirely clear that is what you wanted, but hope this helps. I have more examples, there's a bit more to what I'm doing, since at the bottom line what I wanted was to use my one public IP address to manage more than one service. So that's where Traefik comes in, https://github.com/kingdonb/bootstrap-repo/blob/main/apps/routers/urbit-ships/socryx-topled-ingressroute.yaml

I save them to git, and restore them using GitOps. https://github.com/kingdonb/bootstrap-repo

Using Helm via GitOps, you can pass in ridiculous collections of values that you would never use on the command line, mixing in secrets from secret sources, here is a complicated example (and here is a simpler one that doesn't do any patching.) Hope this helps. Usually when I show people Helm Controller, the reaction I get is "that's exactly what I wanted."

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.