Live data from Hacker News

Google admits Kubernetes container tech is too complex

theregister.com

41–50 of 449 posts

Re: Google admits Kubernetes container tech is too complex

#41
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 mean, it's really too complex to run k8s yourself so Google made an automatic tool so you don't have to.

Re: Google admits Kubernetes container tech is too complex

#42
post #28

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.

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

lol https://github.com/dokku/dokku

Re: Google admits Kubernetes container tech is too complex

#43

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.

My background is in embedded, so I admittedly know extremely little about web development, but whenever I'm curious and sit down to read about microservices and containers and orchestration and all that stuff, my mind starts to numb and I can't help but conclude that 99% of companies that use it probably don't need to. And that they're just a complex way for engineers to keep themselves spinning their wheels and not actually working on an application. Like that guy who insists on doing nothing but refactoring and rearchitecting and moving things from one layer in the stack to the other, re-writing in different languages, integrating new third party libraries that do the same thing their existing third party libraries, but not actually adding anything that improves the product. How did the world get into this situation where you need all this complexity just to deploy and configure not even an application, but part of an application? Amazing!

Re: Google admits Kubernetes container tech is too complex

#45

Earlier quoted context omitted.

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.

Why don't you just create a new Google Account specifically for this?

Re: Google admits Kubernetes container tech is too complex

#46
Not seeing anyone mention it, so I'll just share: https://k8slens.dev/

Lens has been a huge boon for helping us manage our kube cluster and regular devops operations, and even 15 minutes with it helped me grok a number of complex kubernetes concepts that I've struggled with for awhile now.

Everyone who works with k8s for a living should at least know of this tool imho its fantastic with prometheus

Re: Google admits Kubernetes container tech is too complex

#47
post #28

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.

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

Heroku does allow building / deploying Docker images - https://devcenter.heroku.com/categories/deploying-with-docke...

Re: Google admits Kubernetes container tech is too complex

#48

This was glaringly obvious from day one. Containers add vast complexity, add another layer of complexity on top.

Can you explain the whole concept of Kubernetes to someone whose knowledge of computers is limited to making simple webpages with HTML and using Excel/VBA?

This is going to use some amusing metaphors.

Re: Google admits Kubernetes container tech is too complex

#49

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.

Maybe your starting instances are workhorses, but if you go from something like a t3.medium to two it’s a ~$60 / mth increase... Not something I’d personally optimize for.

Also why Docker in the first place? I’m genuinely wondering - in the stacks I run (Express / Python) it doesn’t seem necessary at low scale. Elastic Beanstalk, Heroku, Digital Ocean etc all offer facilities for single-command deploys that work out of the box.

Re: Google admits Kubernetes container tech is too complex

#50
post #42
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!

lol https://github.com/dokku/dokku

Dokku looks super cool but it's still a lot more involved than Heroku. Heroku doesn't make you think about provisioning servers, updating infrastructure, or manually setting up common integrations like backups and logging.

Just to illustrate the point, dokku's docs[0] for logging say "Warning: The default docker-local scheduler will "store" these until the next deploy or until the old containers are garbage collected - whichever runs first. If you require the logs beyond this point in time, please ship the logs to a centralized log server."

Alright, well, that's gonna be a whole lot more work than two click in Heroku to send all my logs to any logging provider of my choice.

[0] https://dokku.com/docs/deployment/logs/

Post reply on HN