Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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



Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

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

Search: