flux2
dokku-scheduler-kubernetes
| flux2 | dokku-scheduler-kubernetes | |
|---|---|---|
| 2 | 4 | |
| 1 | 148 | |
| - | 1.4% | |
| 3.1 | 3.1 | |
| 7 months ago | 23 days ago | |
| Go | Shell | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
flux2
-
Dokku – Free Heroku Alternative
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:
-
Question for declarative GitOps managed shops
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."
dokku-scheduler-kubernetes
-
Dokku – Free Heroku Alternative
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
-
How I made Python/Django Apps deploy themselves
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)
-
RIP Flynn.io
[2]: https://github.com/dokku/dokku-scheduler-kubernetes
What are some alternatives?
tofu-controller - A GitOps OpenTofu and Terraform controller for Flux
rack - Private PaaS built on native AWS services for maximum privacy and minimum upkeep
go-stdlib - OpenTracing instrumentation for packages in the Go stdlib
redbeat - RedBeat is a Celery Beat Scheduler that stores the scheduled tasks and runtime metadata in Redis.
github-action
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
dokku-builder-nix - Dokku plugin to build images using Nix
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
webapp-tutorial - piku experiments with "build a web app fast" prototyping
django-project-template - The Django project template I use, for installation with django-admin.
atlantis - Terraform Pull Request Automation
swarmlet - A self-hosted, open-source Platform as a Service that enables easy swarm deployments, load balancing, automatic SSL, metrics, analytics and more.