K8S

Kubernetes YAML Generator

Generate YAML for Deployment, Service, Ingress, ConfigMap, Secret, PVC, HPA and Namespace — and combine multiple resources into one output file.

Deployment
Service
Ingress
HPA
PVC
probes

resource.yaml

Settings

Resource type

Resource name (metadata.name)

Namespace (optional)

Replica count

Container image

Container port imagePullPolicy

Environment variables (one KEY=VALUE per line) Load from envFrom (optional)

From ConfigMap

From Secret

Resource limits

request cpu request memory

limit cpu limit memory

Add liveness/readiness probe (HTTP GET)

Health check path

Service type Target app label (selector)

port targetPort Protocol

nodePort (optional, 30000-32767)

ingressClassName Host

path pathType

Target Service Port

Enable TLS

secretName

Data (one KEY=VALUE per line)

Data (one KEY=VALUE per line) Base64-encode (data field instead of stringData)

accessMode

Size

storageClassName (optional)

Target Deployment name (scaleTargetRef)

Minimum replicas Maximum replicas

Target CPU (%)

YAML preview

k8s-manifests.yaml

This tool runs entirely in your browser; nothing is sent to a server. The most common fields are covered for each resource — use the "Add to combined output" button to merge multiple resources (e.g. Deployment, Service and Ingress) into one file with a --- separator. This tool is not a replacement for kubectl apply --dry-run=server or a full schema check; review the output before using it in production.

ABOUT

Build Kubernetes manifests from a form: Deployment, Service, Ingress and HPA

Writing Kubernetes YAML from scratch is slow and full of fragile indentation. This tool turns a form into ready-to-apply manifests for Deployment, Service, Ingress, HPA, ConfigMap, Secret and PVC: set replicas, health probes, requests/limits, environment variables and TLS, then apply the output with kubectl apply -f. It also works as a learning aid because you can read the generated YAML line by line.

HOW TO

How to use it

Enter the application name, image and port.
Enable and configure the resources you need (Service, Ingress, HPA …).
Copy the YAML and run kubectl apply -f; you can lint it with the YAML Validator first.

FAQ

Frequently asked questions

What is the difference between ClusterIP, NodePort and LoadBalancer?

ClusterIP is reachable only inside the cluster, NodePort opens a port on every node and LoadBalancer provisions a cloud load balancer. ClusterIP behind an Ingress is usually the best default.

What is the difference between requests and limits?

requests is what the scheduler uses to place the pod; limits is the ceiling. Exceeding the memory limit gets the container OOMKilled.

Is a Secret secure?

A Secret value is only Base64, not encrypted. For real protection use encryption at rest or tools such as External Secrets and Vault.