StatefulSet YAML Generator

A StatefulSet is how you run stateful applications on Kubernetes - databases, message brokers and anything that needs a stable network identity and its own persistent storage. Unlike a Deployment, each pod gets an ordinal name (web-0, web-1, ...) and a dedicated volume that follows it across reschedules. The StatefulSet YAML Generator writes that manifest from a form so you do not have to recall the apps/v1 schema.

You set the StatefulSet name, the required serviceName of its governing headless Service, and optionally a namespace and top-level labels. Then you set replicas, define selector matchLabels (which must match the pod template labels), and add containers with name, image, ports and environment variables. Finally you can add volumeClaimTemplates, each with a name, requested storage, storage class and access modes, so every replica gets its own PersistentVolumeClaim.

The form validates the RFC 1123 names, requires a serviceName and at least one selector label and container, and reports problems in a clear panel. A small statistics strip shows the replica count and number of containers. Everything runs locally and nothing is uploaded, so database sizes and storage classes stay private.

• serviceName - required headless Service name for stable pod DNS.
• Replicas - desired number of pod copies (ordinals 0..N-1).
• Selector matchLabels - must match the pod template labels.
• Pod template labels - separate, selector-aligned section.
• Multiple containers - name, image, ports and env per container.
• volumeClaimTemplates - per-pod PVCs with storage, class and access modes.
• Validation - RFC 1123 names, serviceName, selector and container checks.
• Copy / Download / Print - get statefulset.yaml wherever you need it.

1. Name the StatefulSet. Type a valid RFC 1123 name.
2. Set serviceName. Enter the headless Service name that governs it.
3. Set replicas. Enter the number of pod copies.
4. Add selector matchLabels. They must match the pod labels.
5. Add pod labels. They must match the selector.
6. Add containers. Name, image, ports and env.
7. Add volumeClaimTemplates (optional) with storage and access modes.
8. Watch the preview and export.

Example 1 - Minimal. name db, serviceName db-headless, one container with image postgres:16.

Example 2 - With storage. A volumeClaimTemplate data with 10Gi, ReadWriteOnce.

Example 3 - Multiple replicas. replicas 3 gives pods db-0, db-1, db-2.

Example 4 - Env. Lines POSTGRES_PASSWORD=secret become env entries.

Example 5 - Custom class. storageClassName set to fast-ssd.

• Correct schema - valid apps/v1 StatefulSet.
• Stable identities - serviceName wired in.
• Per-pod storage - volumeClaimTemplates handled.
• Validated - names, serviceName and required fields checked.
• Clean output - empty fields omitted.
• Private - everything runs in the browser.
• Copy, download or print - get the manifest where you need it.