GearOps

GearOps

Compose to Kubernetes

Map a Docker Compose file to Deployments, Services and ConfigMaps, then add probes and resource limits. The result is checked as YAML.

Compose to Kubernetes

Output

The result shows up here. Your input is not written to the log.

Questions

›What is mapped without the model?

Service name, image, deploy.replicas, the first port, environment variables into a ConfigMap, and named volumes into a PersistentVolumeClaim.

›What does the model add?

CPU and memory requests and limits, plus an HTTP probe path. If that step fails validation, built-in defaults are used and the YAML is still checked.

›Do build: sections work?

No. v1 converts services that already have an image. A build-only service is rejected so the output does not invent an image name.

›Is this a full Helm chart?

You get Chart.yaml and values.yaml plus the rendered manifests. Templates with conditionals are out of scope for v1.