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

Ask HN: What is your Kubernetes nightmare?

news.ycombinator.com

Post reply on HN
Print view View original

111–120 of 263 posts

Re: Ask HN: What is your Kubernetes nightmare?

#111

Post by nix23 »

ekidd wrote: post #54

It's odd, but I actually really enjoy using Kubernetes in production. We have a few rules: 1. Read a good intro book cover-to-cover before trying to understand it. 2. Pay a cloud vendor to supply a working, managed Kubernetes cluster. 3. Prefer fewer larger clusters with namespaces (and node pools if needed) to lots of tiny clusters. 3. Don't get clever with Kubernetes networking. In fact, touch it as little as possi…

>My personal Kubernetes nightmare is having to build a cluster from scratch on bare metal.

One's heaven is another one's nightmare, i like building it from scratch because then i know every single knob, and doing a excellent job in documentation makes sure that others have that knowledge too.

But hey since "administrators" is a forgotten art, you are probably better of just buying some black-boxes with terrible performance.

Re: Ask HN: What is your Kubernetes nightmare?

#112

Post by GordonS »

KptMarchewa wrote: post #42
GordonS wrote: post #27

Earlier quoted context omitted.

Compare with Docker Compose files, which still use YAML, but a lot less of it, and less verbose too.

And does a lot less too, since it describes single node deployment, without any complexities behind networking and communication of services on different nodes.

While the file specification is for Docker Compose, Docker Swarm uses the same files, and supports multi-node deployments.

There are a few differences in supported features; for example, IIRC, only Docker Swarm supports `secrets`.

Re: Ask HN: What is your Kubernetes nightmare?

#116

Post by fn1 »

tazjin wrote: post #105
oxff wrote: post #45

You aren't supposed to use a tool made for Google level complexity unless you work with such complexity in the first place.

As a Xoogler I'd say that Kubernetes is harder to use than Google's internal equivalents. It may not be harder to run, but that doesn't matter inside of Google unless you're on the teams responsible for the base layers. My point is, Kubernetes isn't really "made for Google level complexity" - Google only uses it for a handful of cloud products, internal research stuff and not much else.

Why did Google then release the complex Kubernetes to the world than their simpler internal tools?

Re: Ask HN: What is your Kubernetes nightmare?

#117

Post by josephcsible »

guywhocodes wrote: post #93
oxff wrote: post #45

You aren't supposed to use a tool made for Google level complexity unless you work with such complexity in the first place.

Where do I go for my 3-5 node cluster which I want to schedule containers to, run dynamic workloads etc? How do I build a container based DAG in a small cluster today without k8s? Solutions that are not k8s tend to be single programming language/sdk based or not easier to set up. I get the feeling the alternatives are dying off unnaturally fast.

Docker Swarm?

Re: Ask HN: What is your Kubernetes nightmare?

#118

Post by SoftTalker »

Intermernet wrote: post #66
ekidd wrote: post #54

It's odd, but I actually really enjoy using Kubernetes in production. We have a few rules: 1. Read a good intro book cover-to-cover before trying to understand it. 2. Pay a cloud vendor to supply a working, managed Kubernetes cluster. 3. Prefer fewer larger clusters with namespaces (and node pools if needed) to lots of tiny clusters. 3. Don't get clever with Kubernetes networking. In fact, touch it as little as possi…

Kubernetes on bare metal is actually pretty easy. Kubernetes on a hosted solution which doesn't have a managed version is prone to error. Usually on bare metal you can make some guarantees regarding bandwidth and storage speed. Trying to roll out a cluster on a service that can't give you these guarantees is truly a nightmare.

I have tried several times over the past few years to install Kubernetes on bare metal, and it has never worked.

I don't mean installing it on VMs on a laptop, I mean on a real linux cluster of 8 to 32 nodes, with real networks and real switches.

Managing bare metal machines is a cakewalk compared to getting Kubernetes running in-house, at least in my experience.

Obviously the cloud providers do it, so it's possible. But IMO it is something you do only if you have a full-time admin team available to set it up and manage it. It's not by any stretch of the imagination something you install and forget about.

Re: Ask HN: What is your Kubernetes nightmare?

#119

Post by vbezhenar »

ekidd wrote: post #81
jimbokun wrote: post #64

Earlier quoted context omitted.

What are some of the best Kubernetes books?

I personally liked O'Reilly's Kubernetes: Up and Running , which was fairly thorough, and Nigel Poulton's books, which were shorter and focused on the highlights (at least the editions I read). The reason I always recommend that people read a book before getting into Kubernetes is that there are several things that make a lot more sense once someone takes the time to explain them. It actually gave me some 90s nostalg…

Is website documentation not good enough? It looks very thorough. Actually I’d say that it’s rare to encounter so verbose and full documentation nowadays. May be it’s even too deep, but I enjoyed reading it.

Re: Ask HN: What is your Kubernetes nightmare?

#120

Post by rad_gruchalski »

sateesh wrote: post #92
jimbokun wrote: post #64

Earlier quoted context omitted.

What are some of the best Kubernetes books?

Kubernetes in Action by Manning ( https://www.manning.com/books/kubernetes-in-action ) is quite through, good and beginner friendly.

There’s a second edition in MEAP.
Post reply on HN