3 ms·
> The complexity of Kubernetes largely reflects the complexity of the problem. I can solve most of these problems with a simple Linux + systemd in a much more
by erikb 8y ago
> The complexity of Kubernetes largely reflects the complexity of the problem.
I can solve most of these problems with a simple Linux + systemd in a much more readable way and am finished much quicker, even now that I am using k8s full time for 2 years.
So, no. What it represents is the complexity of the community having multiple sources of requirements, and the complexity of the landscape with everybody trying to make a claim with their name+logo without investing too much into a full stack answer.
- jrs95 8y agoHow is systemd going to help you with service discovery, load balancing, autoscaling, automated rolling deployments, etc? That being said, if you don’t need any of those things you probably don’t need Kubernetes either.
- erikb 8y ago> service discovery only used internally and not in a scaling fashion > load balancing External component that is hooked into k8s in some way > autoscaling External component that is hooked into k8s in some way > automated rolling deployments I doubt that many people are at a point yet where they can reliably do that. There are basic assumptions baked into that feature like that the k8s cluster survives until the next update comes out.