Install Kompose - a conversion tool that allows you to convert your Docker Compose code to Kubernetes configuration files Run kompose convert in the same directory as your docker-compose.yml to generate the config files for your Kubernetes cluster. - Source: dev.to / 25 days ago
As stated on their homepage, with Kompose, you can now push the same file to a production container orchestrator!. The tool definitely covers a wide range of Kubernetes features, among which these are meaningless locally but crucial for kubernetes :. - Source: dev.to / 2 months ago
K3s is a small, open source, no nonsense, distribution of Kubernetes. I think you'll find it just as easy to setup as Swarm. The challenge will be that Kubernetes has an entirely different API compared to Docker/Docker Compose. This can be mitigated by a tool called kompose, but using this will limit what you can do on Kubernetes. Source: 5 months ago
Although I recently moved my own services from docker compose to kubernetes using https://kompose.io/ and now the only thing I run with docker compose, currently, is my private docker registry but everything including in kube, are always in their own folders. Source: 5 months ago
You could use Kompose https://kompose.io, just sayin :). - Source: Hacker News / 9 months ago
I haven't run into the need to do that, but there is the Kompose project that exists to help with the conversion (https://kompose.io/)! - Source: Hacker News / 10 months ago
Compose claims to do that. https://kompose.io and https://kubernetes.io/docs/tasks/configure-pod-container/translate-compose-kubernetes/. Source: 11 months ago
Have you looked at https://kompose.io? I have used it to get 80/20 of the work done when converting from docker-compose to k8s. - Source: Hacker News / 11 months ago
I just want to point out that already exist a tool that convert a docker-compose.yml file to several k8s manifests: https://kompose.io . You have to adjust some details because is not perfect, obviously. - Source: Hacker News / about 1 year ago
I frequently recommend Kompose as a k8s beginners tool, but as you've mentioned elsewhere it doesn't work for all scenarios and therefore becomes limiting.... What I do is transition devs to helm as quick as I can. One approach is adopting Devspace (Other similar tools I evaluated were Skaffold + Tilt). This provides developers with the k8s native workflows they need to build, deploy and debug their code against... Source: about 1 year ago
You may be looking for kompose.io ~ a tool for automatically converting compose files into Kubernetes YAML files. Source: over 1 year ago
Thanks for the tip ! I actually edited my yaml file manually since this was my first time but I'll look into kompose.io to make a proper one 😃. Source: over 1 year ago
Lastly if you're already using Docker Compose, then use Kompose to help transition to the Kubernetes way of doing things. I would also recommend investigating some of the emerging dev support tools like Devspace, Skaffold or Tilt. Source: over 1 year ago
When converting a project, I generally recommend using the kompose project. It's good as a starter, but it doesn't cover 100% of my usecases. Source: over 1 year ago
Your next step is to get it running on Kubernetes. To assist the process I suggest a tool called kompose which can generate a starting helm chart. Your objective is to be able to deploy multiple instances of your code into separate namespaces as follows. Source: over 1 year ago
Might not directly answer your question, but you can checkout kompose https://kompose.io. Source: over 1 year ago
Coming back to docker-compose, you can initially use the kompose tool to generate the kubernetes yaml. This will get you up and started. I used this approach to learn how k8s works. A fact you will have to accept is that using Compose is ultimately a dead end, by limiting you to deploying containers to a single machine. Docker Swarm is the only alternative option. Source: almost 2 years ago
There is a tool called kompose that can help translating your docker compose files. Source: almost 2 years ago
Yes it’s a bit much. When I was beginning with kubernetes I was writing Docker compose files first and then converting them to kubernetes using https://kompose.io/. - Source: Hacker News / almost 2 years ago
This article will detail some of the reasons why you should transition from Docker Compose to Kubernetes and provide a step-by-step guide on how to carry out this migration using Kompose, as well as suggestions on other helpful tools for deploying. - Source: dev.to / almost 2 years ago
I share that concern, but I’m reasonably hopeful that Swarm will live a long life, whoever maintains it. Worst-case, my true love is not necessarily Swarm, but the docker-compose spec. I’d be fine deploying to K8s so long as I could use docker-compose manifests (see Kompose). If Swarm disappears, I could manage. If docker-compose disappears, well, I’d unplug my cluster, retire, and become a nomad. Source: almost 2 years ago
Do you know an article comparing Kompose to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Kompose. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.