Hacker News new | past | comments | ask | show | jobs | submit login

Now you can take a really simple Docker compose file and make it complicated with Kubernetes, happy day! Seriously, the complexity and learning curve of Kubernetes will eventually kill the project.



"The complexity and learning curve of vim will kill the project"

"The complexity and learning curve of Emacs will kill the project"

"The complexity and learning curve of LaTex will kill the project"

"The complexity and learning curve of Sendmail will kill the project" <-- The only one that's partially true and it took 35 years.


Expert tools are for experts, they can be hard to use as long as they are really good at doing what they do. If you haven't noticed though, these modern times are all about convenience. We even have delivery services for gasoline, and there was already a gas station on every corner. If Docker (or someone else) makes this stuff super easy, they are going to win.


Sure, and MS Word is way easier to use than Vim or Emacs or LaTex, and has a much bigger market share, but it didn't kill those projects.

Exchange is a lot easier to use than Sendmail, but didn't kill that one either.

When you need power and flexibility, which is generally the case when your project gets to any reasonable size, then you go with the pro tool with the learning curve.


Win the mass market I mean...


Ok, but have you ever tried to deploy docker compose on production. How did it scale for you?

You missed the point. Kompose will generate the Kubernetes config and it can even bring up your application using "kompose up" command. Have some faith and read more about it on kompose.io and use it


Quick correction, Docker 17.03 supports compose files out of the box, in swarm mode. Two commands to deploy and scale. https://docs.docker.com/engine/reference/commandline/stack_d...


This.

GP comment was downvoted into oblivion, but he had a point. Compose (at least, v3/v3.1) is a reasonably simple system, that can describe a fairly complex setup. Kubernetes has a lot of complexity to it. And the question "why do I need it, if there are simpler options?" is left unanswered.


Until you end up working around various shortcomings and then suddenly your yaml files are a mess and almost a framework in themselves.

The Kubernetes files really arent that complex




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: