2 ms·
You're probably looking for Nomad or Mesos honestly. Kubernetes, as designed, is a framework and a rather leaky one in my not so humble and subjective opinion.
by dijit 5y ago
You're probably looking for Nomad or Mesos honestly.
Kubernetes, as designed, is a framework and a rather leaky one in my not so humble and subjective opinion.
it accomplishes a pretty lofty goal (bin-packing, deployment, eventual reconcilation of service and generalising the network/storage so that you don't care about underlying infra) but it does so at a rather heavy cost of complexity and because you can swap out underlying pieces: if you're not on a cloud provider then you're probably going to spend the majority of your life maintaining it.
But, you probably want Nomad, if you're thinking about kubernetes seriously.
- Hallucinaut 5y ago> if you're not on a cloud provider... and lord help you if you are but choose to try to use the same approach across environments and eskew the markup on something like EKS. I've been thumping my head against trying to have a rather trivial HA service working on both a Hyper-V and EC2 cluster equally for weeks and it seems near impossible for reasons no leading lights in the space quite articulates.
- dijit 5y agoI believe your experience in this regard would be a good blog post in of itself that I would love to read.
- throwaway984393 5y agoNomad is neat, but I think it's the wrong paradigm. Say you wanted to write an application that inspects the current state of jobs running in Nomad and modify them. You need to design something specifically to do that within nomad. Essentially you need to integrate their proprietary interface into your application. In a distributed operating system you would just do ls /proc/host/*/* and then issue syscalls or write to files in /proc/ and /sys/. No proprietary interface, it's just operating system primitives. I think it's so simple that it's hard for people to grasp how insanely easier this would be than any current system. Look up Mosix/OpenMosix (but that's an SSI; I'm not saying we should do SSI exactly, it's just an example of the simplicity).