Live data from Hacker News

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

kompose.io

31–40 of 47 posts

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

#31
post #23
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.

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.

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

#33

Earlier quoted context omitted.

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

That sounds annoying. Could it be something with the configuration in your virtualization tool?

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

#34

Earlier quoted context omitted.

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

You can install Docker for Mac, which supports VPN integration out of the box, then install kubernetes on top of that. I heard it works great.

https://docker.com/mac

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

#35
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

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

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

#36
post #34

Earlier quoted context omitted.

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

You can install Docker for Mac, which supports VPN integration out of the box, then install kubernetes on top of that. I heard it works great. https://docker.com/mac

Yes, I've been using Docker for Mac since beta and it does indeed work fine with VPN. It's when I'm using Docker inside minikube where it fails. I didn't realize installing k8 and using with Docker for Mac was straightforward, I'll give it a try. Btw, thx for such an incredible tool!

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

#37
post #18

I used this to get an idea how K8s looked when I wanted to migrate ~500 lines of docker compose YAML config to k8s. The result was sufficiently confusing that we threw it away, but it was helpful to get an idea what we were looking at, and why. We rebuilt the stack from hand, using all the files from the kompose tool as a guide/reference. Later we found that kubectl can dump yaml, I found `kubectl .... -o=yaml[ ...]`…

Links are supposed to be legacy and docker seems to push people into using docker networks, but pragmatically there's something nice about links that make it really fit and simple for many simple use cases where full-blown networks and service discovery are just way overkill.

If you don't use networks then all services are on the default network and can refer to each other by service name, so even without complicated full-blown networks links are superfluous.

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

#38
I'm still pretty new to docker and docker-compose. I've setup a few dev environments but how do you all deal with your app code? Do you mount it or do you copy it. I'm having permission problems with mounting. If you copy what's the workflow like and does kubernetes help at all with any of this?

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

#39

I'm still pretty new to docker and docker-compose. I've setup a few dev environments but how do you all deal with your app code? Do you mount it or do you copy it. I'm having permission problems with mounting. If you copy what's the workflow like and does kubernetes help at all with any of this?

If you use the desktop editions of Docker (Docker for Mac or Docker for Windows), it will handle permissions correctly when mounting.

Currently the server and cloud editions (Docker for Linux, Docker for AWS, Docker for Azure) don't solve the permission problems for performance reasons. But in production you typically don't want or need to mount source code anyway.

If you want to copy instead of mounting, just use the COPY operation in your Dockerfile. https://docs.docker.com

Whether you use Kubernetes or Swarmkit for deploying to production, that takes place later in the workflow.

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

#40
post #35

Earlier quoted context omitted.

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.

Post reply on HN