<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=19408) </details> <!--IssueSummary end--> A lot of developers use Docker Compose for local development. We should make it easy to migrate to a production environment using Auto DevOps by detecting a Docker Compose file (either `docker-compose.yml` or `docker-compose-bundle.dab`) and using `kompose` to convert it into a Kubernetes configuration. From https://gitlab.com/gitlab-org/gitlab-ce/issues/29969: Pecking order: * [x] If project has Helm chart (`./chart/Chart.yaml`) or has variable pointing to a chart (`AUTO_DEPLOY_CHART`), use it * [ ] If project has `docker-compose-bundle.dab`, use it to derive k8s config (using Kompose?) (https://gitlab.com/gitlab-org/gitlab-ce/issues/37588) * [ ] If project has `docker-compose.yml`, use it to derive k8s config (using Kompose?) (https://gitlab.com/gitlab-org/gitlab-ce/issues/37588) * [x] If project has `Dockerfile`, use it, with default k8s config (ideal from Helm chart, but currently from parametrized YML) * [x] If nothing, use Herokuish buildpacks to create Docker image, and default k8s config to deploy ### Links - Auto Deploy should use project's helm chart, if available: https://gitlab.com/gitlab-org/gitlab-ce/issues/29969 Kompose links: - https://github.com/kubernetes-incubator/kompose/blob/master/README.md - http://kompose.io/index - https://news.ycombinator.com/item?id=13783546