11–20 of 47 posts
Hoping this helps with the Kubernetes learning curve. We've just started migrating and keeping track of the terminology has been tough.
Is there a reason to go from docker-compose to kubernetes?
Hoping this helps with the Kubernetes learning curve. We've just started migrating and keeping track of the terminology has been tough.
This tool kompose helped me when I did my first POC on kubernetes since it allowed me to get up and running with something without having to study all the new abstractions and terminology in kubernetes, but pretty quickly I ended up going back over the generated yml files line by line and manually changing stuff. Overall still a helpful tool since many people use Compose in development but need to eventually migrate…
(I'm one of the Kompose maintainers. ;-) )
Earlier quoted context omitted.
agreed, it's surprisingly hard to get your head around initially. minikube helps me personally.
I work on a team who wants to help make this easier. What are the concepts that you think are the most complex?
What I want is a better way to learn hands-on or as I go. Not sure exactly what that looks like.
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[ ...]`…
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[ ...]`…
more generally, what were the biggest upsides / downsides from moving to k8s?!
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[ ...]`…
Very interesting, as we're looking into doing essentially exactly the same very soon. seems even more urgent with docker just having announced free/enterprise editions. Would be very interested in a blog post / some more detail about how it went down! more generally, what were the biggest upsides / downsides from moving to k8s?!
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[ ...]`…
Hoping this helps with the Kubernetes learning curve. We've just started migrating and keeping track of the terminology has been tough.
Is there a reason to go from docker-compose to kubernetes?
https://github.com/kubernetes/charts/tree/master/stable https://github.com/kubernetes/charts/tree/master/incubator
and then very easily tweak them.