I love The Register for that, they just add hyperbole to something which would never come out from a company itself, and often they are right.

K8s is too complex, and I say it as k8s dev(ops) who dreams the next great thing will come soon which will save me from piles of YAMLs and will bring back programming fun ;) /s

K8s isn't too complex for what it does and can do.

it's just that a lot of people think they have to use k8s because it's trendy even it doesn't fit at all their needs and scale. Then they whine it's too complex.

classic PEBCAK issue.

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!

> But it is a surprisingly negative headline.

That's the Register's schtick, they're snarky about everything.

They are usually closer to the truth than evangelists telling us how this new tool is going to solve all our problems.

Reality is too negative for social media.

El Reg's snark is what makes it fun to speak with as they do cut to the heart of it.

GKE Autopilot is still fundamentally Kubernetes and supports the k8s APIs. GKE has simplified a lot of Kubernetes tasks that can be a pain, such as upgrades & scaling, but as many people said on other threads Kubernetes definitely is not for all workloads. For workloads that actually do need to scale then Autopilot removes a lot of the time consuming tasks required to get Kubernetes running and staying running. There are restrictions so check the docs on if it would work for how you use k8s.

Disclosure: I run product for GKE at Google so I'm definitely not a neutral voice on this...

I'm looking for a job now.

Interested in having someone who has had to set up 1000s of containers in k8s and hated all of it?

I almost replied "who would look at Kubernetes and think it needs more layers?" but it sounds like Autopilot is a new cloud service - the customer (hopefully) doesn't interact with the underlying Kubernetes layer. I guess it kinda makes sense.

View from a Googler: Autopilot stitches together existing GKE functions and is just a cluster creation decision. The layer it adds is automating the different tools together and SRE support magic so that we're monitoring it now.

I mean, it's really too complex to run k8s yourself so Google made an automatic tool so you don't have to.

And? None of this is contradictory unless you're reading too much into the headline.

No, it is not a typical Register headline, it is a half of a typical Register headline. However, HN has limits on headline lengths and it has been cut instead of being editorialized which afaik is another HN guidelines violation.

Paging @dang, could we get the title changed? It’s clickbait in its current state.