Show HN: Go from Docker-Compose to Kubernetes with a simple tool • Hacker News Board

Re: Show HN: Go from Docker-Compose to Kubernetes with a simple tool

#21

Post by jedberg » Fri, Mar 03, 2017, 6:32 PM UTC

dollar wrote: post #19

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.

Re: Show HN: Go from Docker-Compose to Kubernetes with a simple tool

#22

Post by hackersvilla » Fri, Mar 03, 2017, 6:40 PM UTC

dollar wrote: post #19

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.

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

Re: Show HN: Go from Docker-Compose to Kubernetes with a simple tool

#23

Post by dollar » Fri, Mar 03, 2017, 6:50 PM UTC

jedberg wrote: post #21

dollar wrote: post #19

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.

Re: Show HN: Go from Docker-Compose to Kubernetes with a simple tool

#24

Post by dollar » Fri, Mar 03, 2017, 6:50 PM UTC

dollar wrote: post #23

jedberg wrote: post #21

Earlier quoted context omitted.

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

Win the mass market I mean...

Re: Show HN: Go from Docker-Compose to Kubernetes with a simple tool

#25

Post by lobster_johnson » Fri, Mar 03, 2017, 6:56 PM UTC

While I appreciate the effort, as a Kubernetes user I can't really recommend this tool.

As a migration tool, it might save some time building your YAML files, but the differences between Compose and Kubernetes are large enough (secret management, for example) that the mapping will be incomplete. But more importantly, the tool itself doesn't lead to a great understanding of Kubernetes itself. In my opinion, the better approach is to learn Kubernetes, then put together your YAML files piece by piece until it all works. Learn by doing.

And it's not useful as a general-purpose tool that abstracts Kubernetes; you need all of the stuff you put in the YAML files. The only way to abstract it is to move one layer up, into a PaaS.

Re: Show HN: Go from Docker-Compose to Kubernetes with a simple tool

#26

Post by markdog12 » Fri, Mar 03, 2017, 7:17 PM UTC

AndyNemmity wrote: post #3

mhluongo wrote: post #2

Hoping this helps with the Kubernetes learning curve. We've just started migrating and keeping track of the terminology has been tough.

agreed, it's surprisingly hard to get your head around initially. minikube helps me personally.

Started using minikube and kompose just yesterday. They're really nice tools. I'm stuck on the fact that minikube doesn't seem to use my vpn connection (fail when attempting to link to library dependencies over vpn).

Re: Show HN: Go from Docker-Compose to Kubernetes with a simple tool

#27

Post by AndyNemmity » Fri, Mar 03, 2017, 7:23 PM UTC

mhluongo wrote: post #13

crb wrote: post #7

Earlier quoted context omitted.

I work on a team who wants to help make this easier. What are the concepts that you think are the most complex?

For me, it's mostly the number of concepts and the fact that they need to be known upfront. None of them are particularly difficult, but I've done ops for a bit and gone from manual sysadmin on bare metal to Puppet to Chef to Salt... then when we started playing with docker, there's the initial learning curve, then a slew of orchestration options to consider. I'm exhausted keeping up with devops tools. What I want is…

Nothing reminds you how little you actually know when you have to pick up docker/k8s for the first time, and realize that it's a long journey to understand every nuance you need to get things done.

Re: Show HN: Go from Docker-Compose to Kubernetes with a simple tool

#28

Post by bglusman » Fri, Mar 03, 2017, 7:38 PM UTC

This looks neat! I'd mirror what codebreaker said and probably in the long term you want to use something like helm.sh to manage your kubernetes yaml, but this may help get started. Also possibly useful for getting started (especially if coming from Heroku or using Foreman with a Procfile) is a gem I built, more or less in anger, out of inability to get a supporting partner to agree to using helm but not wanting to have duplication across deployment files and across environments, so while I don't necessarily reccomend as a long term tool, if you can't or don't want to initially use helm, ky[0] may be a useful stepping stone/bridge solution to avoid a ton of seperate manually maintained, unDRY deployment files with similar or identical env vars and small differences for web vs worker deployments etc.

[0]: https://github.com/stellaservice/ky

Re: Show HN: Go from Docker-Compose to Kubernetes with a simple tool

#29

Post by sebgoa » Fri, Mar 03, 2017, 8:09 PM UTC

I was part of the team that started kompose. The main idea was to help developers who had adopted docker-compose moved to Kubernetes. We understand that this is not a perfect match and there will always be semantic mismatch. Personally, I don't expect folks to use this for production. But, if you started down the road of docker-compose and want an easy way to generate Kubernetes manifests then kompose does the trick. This will get you on the way, and you will start learning Kubernetes primitives.

Re: Show HN: Go from Docker-Compose to Kubernetes with a simple tool

#30

Post by dewiz » Fri, Mar 03, 2017, 8:42 PM UTC

I think it would make more sense to do the opposite, generate Docker compose + files starting from a Kubernetes configuration. k8s features is a superset of Docker Compose, for instance networking, importing files, managing secrets is imho easier and superior in k8s. With docker-compose and Mesos often one has to find workarounds, change the topology, install additional pieces (e.g. service discovery) etc.

To be honest, I don't see a reason to use docker-compose anymore, because minikube gives the full Kubernetes experience locally. It might take a bit to learn k8s, but it's definitely worth it.

"docker-compose up" is perhaps still easier to start with, but as soon as you start working, rather than playing with demos, you hit limitations and want more.