dokku-scheduler-kubernetes
dokku-scheduler-kubernetes copied to clipboard
dokku
Scheduler plugin for deploying applications to kubernetes
We'll need to figure out if we can support both interactive and non-interactive containers, or just non-interactive. https://www.kubernetes.io/docs/concepts/workloads/pods/init-containers
This might require a change on kubedog, or even potentially some way to have a background job wait and terminate the kubedog tail after N seconds...
This is the only thing lacking for Dockerfile support.
Deployments currently use bare environment variables. Although secrets are in plain-text on disk for Dokku, access to the Dokku installation can be fairly locked down, so this isn't a huge...
This currently isn't a thing, but should be. We can either depend on the `iexec` plugin or manually select the container to exec into via https://kubectl.docs.kubernetes.io/pages/container_debugging/executing_a_command_in_a_container.html
We should be able to setup something like minikube or whatever to verify that this plugin actually schedules and interacts with Kubernetes as expected for every change. That will allow...
On a per-app or global basis, we should be able to overwrite the templates. We would then have the following decision tree: 1. If the per-app template exists, use it...
> If you're using Dokku - especially for commercial purposes - consider donating to project development via [OpenCollective](https://opencollective.com/dokku) or [Patreon](https://www.patreon.com/dokku). Funds go to general development, support, and infrastructure costs. >...
Same story as https://github.com/dokku/dokku-scheduler-kubernetes/pull/45 - the Dockerfile specifies either `ENTRYPOINT` or `CMD`
