27 ms·
To the best of my knowledge, there is no such thing as single node production ready k8s cluster. > I don't have anything that needs to autoscale or fail over o
by kansface 9y ago
To the best of my knowledge, there is no such thing as single node production ready k8s cluster.
> I don't have anything that needs to autoscale or fail over or do high availability
You should not be using Kubernetes.
- deleted 9y ago[deleted]
- derefr 9y agoWhat should you be using, then, if your development workflow outputs container-images, and you want to deploy them to your own hardware with remote orchestration + configuration management (and you consider Docker Swarm dead-in-the-water)? That is: what is the “run your own thing-that-is-slightly-lower-level-than-Heroku on a fixed pool of local hardware resources” solution in 2018?
- tomc1985 9y agoI love how there is a plurality of solutions which seem to address everything but your use case...
- moosingin3space 9y agoI would probably just use either docker-compose or systemd+runc for a single node, then use Ansible to manage configurations. Kubernetes strongly assumes you've got a cluster, not a single node.
- 013a 9y agoJust to be clear: You can run Kubernetes on a single node. It just wont be "production ready", because the minimum qualifications of "production ready" has raised in Kube world. A single node running anything isn't production ready, let alone Kube. A single node running a nginx server isn't "production ready" anymore. But Kubeadm will still do it. Kops if you're on AWS. GKE if you're on GCP. Just Docker would be easier to set up though, and that's what the OP means.
- llama052 9y agoTo be honest for something small and simple I’d just throw up a Rancher server and call it from Ansible.