Generate Kubernetes Deployment YAML — Image & Replicas

Scaffold an apps/v1 Deployment from name, image, replicas, and container port. Optional basic HTTP probes assume path /. Starter YAML for local editing — not a production-ready chart.

Loading…
Deployment generator — image & replicas
Emit a minimal apps/v1 Deployment from form fields. Optional probes assume HTTP GET on path / — adjust for real apps.

Developer notes

• Emits apps/v1 with matching labels/selectors. • includeProbes adds httpGet probes on path / and the chosen container port — many apps need different paths or TCP/exec probes. • No resource requests/limits, HPA, or PodDisruptionBudget in v1. • Edit and validate with validate Kubernetes afterward.

Options

Deployment name
metadata.name and default app label/selector.
Namespace
Optional metadata.namespace. Leave empty to omit.
Container image
Image reference for the single container (e.g. nginx:1.27).
Replicas
spec.replicas — desired Pod count.
Container port
containerPort on the container (and probe port when probes are enabled).
Include probes
Adds basic HTTP liveness and readiness probes on path /. Off by default.

When teams pick this route

• Bootstrap a Deployment for a tutorial or ticket. • Align image and replica counts before writing YAML by hand. • Generate a matching name for an Ingress Service backend. • Teach Deployment shape without copying from random blogs.

Worked examples

nginx Deployment, 2 replicas

Form intent

name: web image: nginx:1.27 replicas: 2 containerPort: 80 includeProbes: false

Generated YAML (excerpt)

apiVersion: apps/v1 kind: Deployment metadata: name: web spec: replicas: 2 selector: matchLabels: app: web template: metadata: labels: app: web spec: containers: - name: web image: nginx:1.27 ports: - containerPort: 80

With basic HTTP probes

Form intent

includeProbes: true → liveness/readiness httpGet path / on containerPort

Generated YAML (excerpt)

livenessProbe: httpGet: path: / port: 80 readinessProbe: httpGet: path: / port: 80

Navigate related Kubernetes tools

Expose traffic with generate Ingress, check structure via validate Kubernetes, or browse the Kubernetes hub.

Deployment generator FAQ

Starter YAML limits

What do the optional probes assume?

HTTP GET on path / using the container port. Change path, scheme, or probe type for apps that do not serve /.

Resources, affinity, or HPA?

Not included in v1. Add requests/limits and autoscaling in your editor or GitOps repo.

Is the image pulled or verified?

No. The generator only writes the image string into the manifest.

Production-ready?

No — treat output as a starting point. Review security context, probes, and resources before apply.

More Kubernetes tools in this cluster

Format Kubernetes YAMLValidate Kubernetes YAMLGenerate Kubernetes IngressGenerate Kubernetes DeploymentFormat Helm values.yaml

Looking for converters, encoders, formatters, and minifiers in one place? Developer tools hub Open the curated developer tools catalogue.

Kubernetes

K8S
Format Kubernetes YAML
K8S
Validate Kubernetes YAML
K8S
Generate Kubernetes Ingress
K8S
Format Helm values.yaml

View all

Minify

Beautify

Unminify

Conversion

JSON

YAML

XML

CSV

TOML

TSV

SQL

HTML

Markdown

Properties

INI

JSON Tools

SVG Tools

DevOps & Infra

CI/CD

Logs & observability

Security & tokens

API & schemas

Encoding

Developer utilities

Serialization