Google admits Kubernetes container tech is too complex
theregister.com
Google admits Kubernetes container tech is too complex
1–10 of 449 posts
Re: Google admits Kubernetes container tech is too complex
#2Googler, opinions are my own.
Direct link to the docs: https://cloud.google.com/kubernetes-engine/docs/concepts/aut...
Google has a tool by the same name (autopilot) internally that does close to the same thing. There was a paper published on it 10 months ago talked about here: https://news.ycombinator.com/item?id=22980467
Re: Google admits Kubernetes container tech is too complex
#3I can't fight the feeling that this is all circling back to the application server stuff that was popular for a time. And, really, I can't tell when those went so wrong. :(
Re: Google admits Kubernetes container tech is too complex
#4From the TA: The maximum number of pods per node is 32, as opposed to 110 on standard GKE.
This is sad.. I don't understand why providers do it. It makes it very expensive to run small staging clusters. There is some reference on the current state here:
https://docs.google.com/spreadsheets/u/0/d/1yhkuBJBY2iO2Ax5F...
Re: Google admits Kubernetes container tech is too complex
#5I think the single biggest mistake people make with Kubernetes is implementing it too soon. Last company I worked for spent piles of time fighting K8s when a simple well implemented cluster would have done the job.
It makes a lot of sense to build portable infrastructure, but you can scale a long ways with much simpler technologies.
Re: Google admits Kubernetes container tech is too complex
#6Sadly, this is a typical Register headline.
Google did not say "Kubernetes is too complex" but rather, they are making this new tool - called Autopilot - that is an abstraction layer on top of Kubernetes for certain types of applications / companies.
This Autopilot system still uses Kubernetes AFAICT.
Re: Google admits Kubernetes container tech is too complex
#7[deleted]
Re: Google admits Kubernetes container tech is too complex
#8I think the single biggest mistake people make with Kubernetes is implementing it too soon. Last company I worked for spent piles of time fighting K8s when a simple well implemented cluster would have done the job. It makes a lot of sense to build portable infrastructure, but you can scale a long ways with much simpler technologies.
Build debs, use the package manager. VMs are already an artificial abstraction, just use them.
Re: Google admits Kubernetes container tech is too complex
#9Sadly, this is a typical Register headline. Google did not say "Kubernetes is too complex" but rather, they are making this new tool - called Autopilot - that is an abstraction layer on top of Kubernetes for certain types of applications / companies. This Autopilot system still uses Kubernetes AFAICT.
They have a quote from the GKE lead directly saying "Despite 6 years of progress, Kubernetes is still incredibly complex."
But it is a surprisingly negative headline. Autopilot sounds like a cool tool to simplify container orchestration!
Re: Google admits Kubernetes container tech is too complex
#10What happened to "focus on the business logic / application"?
Are we just making rabbit holes out of rabbit holes of abstraction using kubernetes?
I just use and push code to Heroku and I'm done for the day, simple. NoOps I call it.
I wish more tools and platforms were like this.