neo-docker-to-k8s-manifests
by martinforsulu
DevOps & CloudBrief
Automatically generate optimized Kubernetes deployment manifests from Dockerfile and docker-compose configurations.
Description
What This Skill Does
Converts Dockerfile and docker-compose.yml files into Kubernetes deployment manifests. Outputs Deployment, Service, Ingress, ConfigMap, and PVC resources with resource limits, health probes, and security context applied automatically.
Eliminates the manual work of translating Docker metadata into valid k8s YAML while also applying resource estimates, probes, and security context that are easy to miss when writing manifests by hand.
When to Use It
- Migrating a Docker Compose app to a Kubernetes cluster
- Adding liveness and readiness probes to an existing k8s deployment
- Generating a starting point for k8s manifests from a legacy Dockerfile
- Converting a multi-service compose file into separate k8s resources
- Applying security hardening defaults to a new Kubernetes deployment
Example Workflow
User asks: Convert my docker-compose.yml to Kubernetes manifests
- 1
Reads and parses the docker-compose.yml to extract services, ports, volumes, and environment variables
- 2
Detects application types to estimate CPU and memory resource limits
- 3
Generates a Deployment manifest per service with liveness, readiness, and startup probes
- 4
Creates Service, Ingress, ConfigMap, and PersistentVolumeClaim resources as needed
- 5
Validates all generated manifests against Kubernetes schemas and writes them to the output directory
A set of production-ready .yaml files in ./k8s/ covering all services from the compose file
Installation
clawhub install martinforsulu/neo-docker-to-k8s-manifestsRun the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.