bootstrap-repo VS flux2

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."

My go-to stack is Prometheus and Grafana with kube-prometheus-stack chart. I'm sure I'm not configuring it well. There are too many leaps I couldn't follow directly, and there's something about how arrays merge in YAML that makes it harder to write a config like this in Helm... but this one goes so far as making alerts to Slack with Alertmanager that work out of the box

https://github.com/kingdonb/flux2/blob/monitoring/manifests/...

:sunglasses:

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."