Anyone using Docker Kanvas to go from Compose to Kubernetes? How does it compare to Helm?

Docker released Kanvas earlier this year as a Docker Desktop extension (built with Layer5/Meshery) and the pitch is pretty compelling: take your existing docker-compose.yml, import it into Kanvas, and it generates Kubernetes manifests, Helm charts, or even Terraform configs automatically. There’s a visual designer mode and an operator mode for managing live clusters.

I’ve been playing with it for a small side project and it does work for simple setups. Import a Compose file, drag things around in the visual editor, hit deploy, and you get a working Kubernetes deployment. It even generated the Services and Ingress resources correctly for a basic web app + postgres + redis stack.

But I have questions before considering it for anything more serious:

1. How does the generated output compare to hand-written Helm charts?

The Kubernetes manifests Kanvas produces look clean enough, but I’m wondering if anyone’s done a side-by-side comparison with a well-structured Helm chart for the same application. Are there things Helm handles (like conditional logic with if/else, shared helpers, or complex value overrides) that Kanvas just can’t express?

2. CI/CD integration

Right now it seems very Docker Desktop focused. Is there a CLI or API that could plug into a GitHub Actions or GitLab CI pipeline? The visual editor is nice for exploration, but we can’t have developers clicking buttons to deploy to production.

3. Multi-environment configs

With Helm, we use different values files for dev/staging/prod (values-dev.yaml, values-prod.yaml, etc.). How do people handle environment-specific configuration in Kanvas? Is there an equivalent pattern?

4. Vendor lock-in concerns

Kanvas generates standard Kubernetes YAML, which is great. But if we build our workflow around the visual designer and its abstractions, are we creating a dependency on Docker’s tooling that could bite us later?

Would love to hear from anyone who’s tried it beyond toy projects, especially in a team setting where multiple people need to collaborate on infrastructure configs.


Seed content posted by the DevForums team to help get our community started. Have a better answer? Jump in!