Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google admits Kubernetes container tech is too complex

theregister.com

Post reply on HN
Print view View original

31–40 of 449 posts

Re: Google admits Kubernetes container tech is too complex

#31

Post by hliyan »

colesantiago wrote: post #10

What 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.

In my day, we used to just insert the server into the rack, plug it into the network, terminal into it and configure it. I'm not being sarcastic here. There was a clear correspondence between what we were doing and what it meant for the infrastructure. Now there are so many layers of abstractions that we've basically forgotten it's all just CPUs, hard disks, memory modules and network connections.

Re: Google admits Kubernetes container tech is too complex

#32

Post by Clewza313 »

gundmc wrote: post #9
ohmywhat wrote: post #6

Sadly, 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!

> But it is a surprisingly negative headline.

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

Re: Google admits Kubernetes container tech is too complex

#33

Post by raverbashing »

fen4o wrote: post #13

I understand their rationale. We manage thousand Kubernetes clusters and end-users can find lots and lots of creative way to shoot themselves in the foot: - I can store anything in a secret? Let's have thousands of cat images. Etcd then stops working because we have over 2GB of funny cats in the key store. - I can run a root Pod? Lets mount the docker socket and start building images with it. Oh and by the way, I nev…

Oh yes secret management with kubectl is needlessly complicated

Sure just put your secret data on a file then we'll use your file name as the key of the secret.

Cronjobs sometimes have weird bugs as well.

A lot of its complexity is due to the fact it's an evolving system, that's fine. But I see that some things end up way more complex or unreliable than it needs due to overengineering or use cases no one needs

Re: Google admits Kubernetes container tech is too complex

#35

Post by imhoguy »

ohmywhat wrote: post #6

Sadly, 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.

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

Re: Google admits Kubernetes container tech is too complex

#36

Post by trinovantes »

Kubernetes has to be most complex software I've ever tried to learn. I eventually gave up and decided to stick with simple single machine docker-compose deployments. I figure by the time any of my personal projects actually need to scale beyond 1 machine, I'd probably have enough revenue that I can afford to hire someone else to worry about it.

Re: Google admits Kubernetes container tech is too complex

#37

Post by Gigablah »

ohmywhat wrote: post #6

Sadly, 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.

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

Re: Google admits Kubernetes container tech is too complex

#38

Post by anothernewdude »

ohmywhat wrote: post #6

Sadly, 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.

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

Re: Google admits Kubernetes container tech is too complex

#39

Post by threeseed »

colesantiago wrote: post #10

What 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.

And Heroku is great for simple apps.

When you start having a lot of pieces to manage eg. cache, database, auth, multiple applications then Kubernetes comes into its own.

Because then you can scale, monitor, trace, debug, log, backup, audit, encrypt and visualise all of those pieces in exactly the same way.

And do it irrespective of which cloud you use or whether it's even in the cloud at all.

Re: Google admits Kubernetes container tech is too complex

#40

Post by monsieurbanana »

Clewza313 wrote: post #30
aroman wrote: post #28

Earlier quoted context omitted.

Mind blowing to me that "Heroku but with docker images" doesn't seem to exist. Would love to be corrected!

That's pretty much Cloud Run, no? https://cloud.google.com/run/

I'm looking for something like that, but I'm afraid of using any google developer services, such as GCP, for personal projects. What if I breach their TOS somehow and get banned, or what if I didn't breach their TOS and still get banned?

Can't afford to test my luck until I've finished migrating all my accounts off my gmail.

Post reply on HN