dokku-scheduler-kubernetes VS flux2

There are both Kubernetes[1] and Nomad[2] plugins. I'm also building schedulers for AWS Lambda, Compose (which I guess also sorta provides Azure ACI and AWS ECS support), and Swarm.

You can also scale individual process types (so anything in your Procfile) via our `ps` plugin[3]. All plugins should support this, so you don't need to learn a new set of commands for alternative schedulers.

- [1] Kubernetes Scheduler Plugin: https://github.com/dokku/dokku-scheduler-kubernetes

https://github.com/dokku/dokku-scheduler-kubernetes#function...

> The following functionality has been implemented: Deployment and Service annotations, Domain proxy support via the Nginx Ingress Controller, Environment variables, Letsencrypt SSL Certificate integration via CertManager, Pod Disruption Budgets, Resource limits and reservations (reservations == kubernetes requests), Zero-downtime deploys via Deployment healthchecks, Traffic to non-web containers (via a configurable list)

[2]: https://github.com/dokku/dokku-scheduler-kubernetes

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