3 ms·
I'm a long time happy DO user, this is exciting. I've been managing multiple docker apps (using docker-compose) on DO for years. Is there a guide I can use to
by xrd 8y ago
I'm a long time happy DO user, this is exciting.
I've been managing multiple docker apps (using docker-compose) on DO for years. Is there a guide I can use to transition my apps from docker-compose to k8s? I've dabbled in k8s, but am not an expert at all.
Any suggestions?
- strukturedkaos 8y agoDitto - I would also be interested in a similar migration guide from docker-compose to k8s in DO.
- thinkshiv 8y agocheck this out: https://github.com/kubernetes/kompose https://github.com/kubernetes/kompose
- bdcravens 8y agoYou can actually go direct now: https://blog.docker.com/2018/12/simplifying-kubernetes-with-docker-compose-and-friends/ https://blog.docker.com/2018/12/simplifying-kubernetes-with-...
- thinkshiv 8y agoCheck this out: https://github.com/kubernetes/kompose https://github.com/kubernetes/kompose and this article may help: https://www.digitalocean.com/community/tutorials/modernizing-applications-for-kubernetes https://www.digitalocean.com/community/tutorials/modernizing...
- bdcravens 8y agoAbility to go direct from docker-compose to Kubernetes (I believe kompose just compiles into k8s config files) was recently announced: https://blog.docker.com/2018/12/simplifying-kubernetes-with-docker-compose-and-friends/ https://blog.docker.com/2018/12/simplifying-kubernetes-with-...
- marmot777 8y agoDO is my favorite hosting service for sure.
- bdcravens 8y agoKompose has been around for a little while, which essentially "compiles" your docker-compose.yml into K8S config files. However, Docker recently announced ability to deploy directly from docker-compose: https://blog.docker.com/2018/12/simplifying-kubernetes-with-docker-compose-and-friends/ https://blog.docker.com/2018/12/simplifying-kubernetes-with-... My understanding is that you'll still need to do some work, especially if you are building via compose instead of pointing to an image on a registry.
- xrd 8y agoYes, there is still a lot of work that requires a lot of knowledge about k8s. Kompose up does not just work, but it seems like DO could make that a simple set of commands with better documentation.
- xrd 8y agoI've read the replies. I've found that kompose does not give me the "try before you buy" experience I was hoping for. For example, on another major cloud providers, they allow me to push up and deploy my container (stored in their registry) without even having docker installed on the client machine. Of course, I would want to test and play with k8s before I used it in production. But, with kompose I still feel like I need to understand a lot about k8s. With docker compose I have almost forgotten everything but docker-compose build && docker-compose compose up I think this is why Heroku was so popular. Just change git push to heroku push and try it out. Since at least a few people align with my comment by up voting it, it seems like enough people would love an easy transition path from docker compose to k8s. This would be a killer feature for Digital Ocean: create a new cluster and then run a few well documented commands and your application is running inside DO on k8s. A guy can dream, right? DO has always had the best documentation on just about everything technical; maybe this is just an opportunity to write up the steps? Those two documents so far, even the one from docker, still require a lot of extra reading for someone who has used docker compose for a long time.