3 ms·
Kind is explicitly not for production workloads[0]: Non-Goals: Being “production workload ready” - kind is meant to be used: for testing Kubernetes itse
by bndw 7y ago
Kind is explicitly not for production workloads[0]:
Non-Goals: Being “production workload ready” - kind is meant to be used:
for testing Kubernetes itself
for testing against Kubernetes (EG in CI on Travis, Circle, etc.)
for “local” clusters on developer machines
NOT to host workloads serving user traffic etc.
K3s seems happy to support production workloads. It's a single binary and gets you a cluster in one command:
curl -sfL https://get.k3s.io | sh -
sudo kubectl get nodes
Personally, I use both Kind and k3s. Kind is great for running locally and k3s is awesome for single-node kubernetes on a vps.
[0] - https://kind.sigs.k8s.io/docs/contributing/1.0-roadmap/#non-goals https://kind.sigs.k8s.io/docs/contributing/1.0-roadmap/#non-...
- lhuser123 7y agoWhat are the benefits you find in using Kubernetes for a single-node cluster on a vps?
- hn_mattfreeman 7y agoIn that scenario it's kind of like a much nicer systemd for docker containers.
- bndw 7y agoI host a few personal websites and Kubernetes allows me abstract the server setup. I don't need a highly available cluster and found k3s on a single node to be a nice replacement for manually configuring a reverse proxy, systemd services, deployment scripts, etc.
- naniwaduni 7y ago"not meant to be used" mostly just means that when something breaks, you're on your own. Which, you know, you were anyway.