Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- How is this different than Cockpit?by s09dfhks
- Manage containers and env values without effortby r2ob
- Why would you manage a server with Kubernetes in any case??by temp0826
- Because otherwise you have to use this! Or some other DIY gobbled together whatever.
That's tongue in cheek but a pretty hard check too, imo. The thing of it is, I like kubernetes, I think you'd have to be mad to opt to re-figure this all out, to get adequate parity. But but but I do want there to be competition, evolution, I want people trying things.
Usually though the competition is trying to do far less. When people eskew Kube, it's usually because they think they are right sizing their approach, "you might not need Kube". Usually they are trying to avoid building an API based platform that scales across different concerns (no CRD, no api-server). Usually they are trying to avoid autonomics, avoid OODA loops, avoid self healing. Usually the desired state management is fairly limited.
I'd like to see more attacks on kubernetes that are from above, and not below. Why is yours better? Being smaller, doing less, is so far the only reason I've heard, the only reason I've seen people go for, what to me, is their own personal tilt at the windmills that Kube has done. This is a hard foe to try to tilt at, and I wish yee tilters the best, I just think it needs to be a more principled still general approach to actually be meaningful. Otherwise: you should Kube.
- Kubernetes does not manage servers anyway. You still need something to put Kubernetes on those servers.
- I have to ask why someone would choose this over ansible, ssh, and a proper monitoring and metrics stack.
Something like this allows unconstrained config drift with no audit trail.
by codeduck - You shouldn't. If you are small enough, use Docker Compose with Ansible.
Once you get big enough, Kubernetes for 99% of companies, is next logical step.
by stackskipton