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

Is K8s Too Complicated? 

jmoiron.net

Post reply on HN
Print view View original

81–90 of 171 posts

Re: Is K8s Too Complicated? 

#81

Post by ad_hominem »

Filligree wrote: post #38
ad_hominem wrote: post #20

Earlier quoted context omitted.

You may want to update your tutorial to use cert-manager because kube-lego is in maintenance-only mode

You mean, it's stable. That sounds like a good reason to use it, not to avoid it.

Not really; I had an issue that silently broke renewals. When I found the open issue that corresponded to it the maintainers were herding people to cert-manager. There are a lot of issues where they are doing that (besides very obviously at the top of the README with warning symbols).

At the very least it's eventually going to break on newer versions of Kubernetes. Maintenance-only != LTS.

Re: Is K8s Too Complicated? 

#82

Post by matthewmacleod »

tarr11 wrote: post #11

If you follow that link on Twitter, there are a lot of reasonable answers to his (rhetorical?) question - "In a single tweet — can you name a technical benefit you and your team have gained by switching to Kubernetes?" "Sensible configuration, fast deployments, awesome community, and flexible control plane...among others" "single root of truth for configuration" "predictable deploys" "Standardized orchestration, whic…

I would argue that those were benefits of switching to any containerised infrastructure with an orchestrator, though. You could probably obtain most of those benefits with Nomad or Mesos.

Re: Is K8s Too Complicated? 

#83

Post by wpietri »

pstadler wrote: post #13
hacknat wrote: post #5

Right tool for the right job. Is K8s too complicated? For some use cases it is. They probably should do a better job of discouraging certain use cases, but calling their elevator pitch “bullshit” is hyperbolic. There are exceptions to every rule, but a good rule of thumb is cluster size. If you’re managing less than 25 servers than K8s is probably over kill. As you start to creep north of 40 servers K8s really starts…

Even though I fully agree with you, running a little 3 node cluster just for fun is amazing. Thanks to Rook and an Nginx ingress controller with kube-lego, I’m able to deploy applications leveraging distributed storage and getting tls secured endpoints without a single ssh session. This, in my point of view, is absolutely powerful. Shameless plug, I‘ve been working on a project explaining how to run small scale clust…

Ooh, thanks, this is just what I've been looking for.

Re: Is K8s Too Complicated? 

#84

Post by justinsaccount »

zie wrote: post #54
Filligree wrote: post #39

Earlier quoted context omitted.

Okay, how about for a tiny budget?

Nomad (www.nomadproject.io) is what I would recommend. Nomad is ONLY a task scheduler across a cluster of machines. Which is why it’s not rocket science, nor is it operationally complex. You say I need X cpu and X memory and I need these files out on disk(or this docker image) and run this command. It will enforce your task gets exactly X memory, X cpu and X disk, so you can’t over-provision at the task level, Docker…

> You can do load balancing and all the other things k8s does

Nomad can do many of the things that k8s does, and even some things that k8s can't, but it does not do all the things that k8s does. For example, nomad doesn't have network policies.

Also, just to approach the base level of functionality and security in k8s you need to setup consul as well and bootstrap all the tls stuff, and at that point it's not much more work to get k8s going.

Nomad is pretty cool, and is rapidly catching up to k8s, it will be interesting to see what happens in the long run.

Re: Is K8s Too Complicated? 

#85

Post by rco8786 »

matthewmacleod wrote: post #82
tarr11 wrote: post #11

If you follow that link on Twitter, there are a lot of reasonable answers to his (rhetorical?) question - "In a single tweet — can you name a technical benefit you and your team have gained by switching to Kubernetes?" "Sensible configuration, fast deployments, awesome community, and flexible control plane...among others" "single root of truth for configuration" "predictable deploys" "Standardized orchestration, whic…

I would argue that those were benefits of switching to any containerised infrastructure with an orchestrator, though. You could probably obtain most of those benefits with Nomad or Mesos.

Maybe. But the question wasn’t about the advantages of k8s over other containerization systems.

Re: Is K8s Too Complicated? 

#86

Post by matthewmacleod »

rco8786 wrote: post #85
matthewmacleod wrote: post #82

Earlier quoted context omitted.

I would argue that those were benefits of switching to any containerised infrastructure with an orchestrator, though. You could probably obtain most of those benefits with Nomad or Mesos.

Maybe. But the question wasn’t about the advantages of k8s over other containerization systems.

I know, you’re right of course.

It’s kinda like all those “we rewrote our Ruby app in Go and it’s 1000x faster so Go is awesome” articles. Containerisation is good for those things, but it’s still possible that Kubernetes is an excessively complex solution to the problem!

Re: Is K8s Too Complicated? 

#88

Post by jon-wood »

znpy wrote: post #23
hacknat wrote: post #5

Right tool for the right job. Is K8s too complicated? For some use cases it is. They probably should do a better job of discouraging certain use cases, but calling their elevator pitch “bullshit” is hyperbolic. There are exceptions to every rule, but a good rule of thumb is cluster size. If you’re managing less than 25 servers than K8s is probably over kill. As you start to creep north of 40 servers K8s really starts…

Interesting, what do you think should be used to manage a cluster of less than 25 machines?

At less than 25 machines throw it on Heroku. Yes, it’ll be more expensive hardware wise, but you’ll probably save that much in not operating you’re own servers.

Re: Is K8s Too Complicated? 

#89

Post by raesene9 »

Filligree wrote: post #38
ad_hominem wrote: post #20

Earlier quoted context omitted.

You may want to update your tutorial to use cert-manager because kube-lego is in maintenance-only mode

You mean, it's stable. That sounds like a good reason to use it, not to avoid it.

From the Kube-lego github page, it looks like the last version of k8s is supports is 1.8, which will only be supported until 1.11 comes out.

So sounds more like it's deprecated than stable.

Re: Is K8s Too Complicated? 

#90

Post by barnabee »

013a wrote: post #34

"In a single tweet — can you name a technical benefit you and your team have gained by switching to Kubernetes?" "The missing step in a comprehensive OSS devops strategy, from code (git) build (Docker) test (Docker) to deploy (Kube), which enables push-button CICD like no one has gotten right since Heroku."

If they'd got it as right as Heroku then deployment (or CD configuration) would be a one liner once a server is set up and scaling etc. would be configurable via a very simple web console or CLI.

Unless I missed something, last time we tried k8s (admittedly ~6 months ago) it was woefully far from that goal.

Post reply on HN