Kubernetes YAML generator

Generate, validate and export production-style K8s manifests across core, security and enterprise templates.

Tier 1 templates (core)

Tier 2 templates (security)

Tier 3 templates (enterprise)

Core settings

App name

Namespace

Image

StatefulSet image

Replicas

Container port

Service port

Service type

Ingress host

PVC size

PVC access mode

PVC storage class

PVC mount path

Autoscaling, Jobs, Daemon and Quotas

HPA min replicas

HPA max replicas

HPA CPU target %

Cron schedule

Job image

Cron image

Daemon image

Quota pods

Role verbs (csv)

Job commandCron commandDaemon command

Resource limits calculator

CPU request

CPU limit

Memory request

Memory limit

ConfigMap / Secret / Env

Environment (KEY=VALUE)ConfigMap dataSecret data (KEY=VALUE)

Generated manifests

Valid YAML (3 document(s)).

apiVersion: v1
kind: Namespace
metadata:
  name: production
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: my-app
  namespace: production
spec:
  replicas: 2
  selector:
    matchLabels:
      app: my-app
  template:
    metadata:
      labels:
        app: my-app
    spec:
      containers:
        - name: my-app
          image: nginx:latest
          ports:
            - containerPort: 80
          env:
            - name: NODE_ENV
              value: production
          resources:
            requests:
              cpu: 100m
              memory: 128Mi
            limits:
              cpu: 300m
              memory: 384Mi
---
apiVersion: v1
kind: Service
metadata:
  name: my-app-svc
  namespace: production
spec:
  selector:
    app: my-app
  type: ClusterIP
  ports:
    - port: 80
      targetPort: 80

Need more than a template?

Want a hand with the infrastructure side?

I set up CI/CD, Kubernetes and cloud platforms that keep releases routine.

DevOps engineering →

How to use the Kubernetes YAML generator

Fill in an app name, image and a few settings and the tool writes manifests for 19 kinds of resource: Namespace, Deployment, StatefulSet, Service, Ingress, ConfigMap, Secret, PersistentVolumeClaim, HorizontalPodAutoscaler, Job, CronJob, DaemonSet, NetworkPolicy, ResourceQuota, LimitRange, PodDisruptionBudget, ServiceAccount, Role and RoleBinding. A resource calculator suggests CPU and memory requests and limits.

Set the app name, namespace, image, replicas and ports.
Turn on the templates you want. They are grouped as core, security and enterprise.
Check the generated YAML, then copy or download it and apply it with kubectl.

Worked examples

Applying the output

kubectl apply --dry-run=server -f manifests.yaml
kubectl apply -f manifests.yaml

A server-side dry run checks the manifests against your cluster's real API before anything changes.

Mistakes to avoid

Relying on the built-in check
The validation confirms that the YAML parses and that each document has an apiVersion and a kind. It is not a schema check. Run kubectl apply --dry-run=server or a tool such as kubeconform for that.
Forgetting probes
The generated Deployment sets resource requests and limits but no readiness or liveness probes. Add them, or Kubernetes cannot tell a starting pod from a broken one.
Setting an autoscaler without CPU requests
A HorizontalPodAutoscaler that targets CPU percentage needs CPU requests on the pods and a metrics server in the cluster. Without both, it does nothing.
Believing a Secret is encrypted
Kubernetes Secret values are only base64-encoded. Turn on encryption at rest for etcd, and keep real secrets out of Git.
Using the latest image tag
A pod that restarts may pull a different image than the one it ran before. Use a specific version or a digest.

Questions people ask

Does it work for any cluster?: The manifests use standard Kubernetes APIs, so they apply to EKS, GKE, AKS and local clusters such as kind or minikube. An Ingress also needs an ingress controller installed in the cluster.
What do the resource profiles mean?: Small, medium and large fill in starting values for CPU and memory requests and limits. They are sensible defaults, not measurements. Watch real usage and adjust.

Docker Compose Generator
Nginx Config Generator
DevOps Architecture & Platform Reliability (the service behind tools like this one)
How one config change takes down production, and how to contain yours (article)