Try it

Workload name

Namespace (optional)

Container image

Replicas

Container port

Port name

Lowercase DNS-1123 label.

Service type

Environment (KEY=value per line)

CPU request

CPU limit

Memory request

Memory limit

File: web.yaml
Selector: web
Content: # Generated in the browser — review this file and adapt it to your project before committing. apiVersion: apps/v1 kind: Deployment metadata: name: web namespace: default labels: app: web spec: replicas: 1 selector: matchLabels: app: web template: metadata: labels: app: web spec: containers: - name: web image: nginx:1.25 ports: - name: http containerPort: 80 resources: requests: cpu: 100m memory: 128Mi limits: cpu: 500m memory: 512Mi --- apiVersion: v1 kind: Service metadata: name: web namespace: default labels: app: web spec: type: ClusterIP selector: app: web ports: - name: http port: 80 targetPort: http

# Generated in the browser — review this file and adapt it to your project before committing.
apiVersion: apps/v1
kind: Deployment
metadata:
  name: web
  namespace: default
  labels:
    app: web
spec:
  replicas: 1
  selector:
    matchLabels:
    app: web
  template:
    metadata:
      labels:
    app: web
    spec:
      containers:
        - name: web
          image: nginx:1.25
          ports:
            - name: http
              containerPort: 80
          resources:
            requests:
              cpu: 100m
              memory: 128Mi
            limits:
              cpu: 500m
              memory: 512Mi
---
apiVersion: v1
kind: Service
metadata:
  name: web
  namespace: default
  labels:
    app: web
spec:
  type: ClusterIP
  selector:
    app: web
  ports:
    - name: http
      port: 80
      targetPort: http

Supported formats

Input: text
Output: text

Privacy

Runs entirely in your browser. Your input is never uploaded, stored, or sent to a third party.

Processing: In your browser
Privacy level: Browser only

Generated a Deployment and Service for "web" with 53 line(s).

How it works

Wrote the Deployment metadata, labels and replica count.
Set the container image to "ghcr.io/example/web:1.4.0" and exposed port 3000.
Emitted a Service whose selector matches the Deployment labels.

The manifest is a starting point: review namespaces, probes, resources and policies for your cluster.
No network request is made; the YAML is assembled in this page.

Methodology

Validate the name, namespace, image, replica count, port and environment keys.
Assemble the Deployment object with matching pod and selector labels, then the Service object with the same selector.
Join both documents with `---` and prepend a review header.

Usage

Enter a DNS-1123 workload name and image.
Set the replica count, container port, resources and optional environment variables.
Choose a Service type and copy the generated manifests.

Examples

These are examples, not current values: they use fixed inputs, while the interactive tool computes live results in your browser.

Node web service

{
  "name": "web",
  "namespace": "default",
  "image": "ghcr.io/example/web:1.4.0",
  "replicas": 2,
  "port": 3000,
  "containerPortName": "http",
  "env": "NODE_ENV=production\nPORT=3000",
  "cpuRequest": "100m",
  "cpuLimit": "500m",
  "memoryRequest": "128Mi",
  "memoryLimit": "512Mi",
  "serviceType": "ClusterIP"
}

Example result

{ "filename": "web.yaml", "content": "# Generated in the browser — review this file and adapt it to your project before committing.\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n name: web\n namespace: default\n labels:\n app: web\nspec:\n replicas: 2\n selector:\n matchLabels:\n app: web\n template:\n metadata:\n labels:\n app: web\n spec:\n containers:\n - name: web\n image: ghcr.io/example/web:1.4.0\n ports:\n - name: http\n containerPort: 3000\n env:\n - name: NODE_ENV\n value: \"production\"\n - name: PORT\n value: \"3000\"\n resources:\n requests:\n cpu: 100m\n memory: 128Mi\n limits:\n cpu: 500m\n memory: 512Mi\n---\napiVersion: v1\nkind: Service\nmetadata:\n name: web\n namespace: default\n labels:\n app: web\nspec:\n type: ClusterIP\n selector:\n app: web\n ports:\n - name: http\n port: 3000\n targetPort: http\n", "lineCount": 53, "sections": [ "Deployment", "Service" ], "kind": "Deployment", "selector": "web" }

Limitations

What the generated manifest includes

The Deployment carries the replica count, a pod template with the image and named container port, optional resource requests and limits, and optional environment entries. The Service selects the same `app` label.

Frequently asked questions

Is the manifest applied to a cluster?: No. The tool only assembles YAML in the page; run `kubectl apply --dry-run=client -f` yourself to check it.
Where do secrets go?: Never in this manifest. Reference a Secret with valueFrom and keep real values out of the generated file.

Sources

Kubernetes API reference — Deployment — CNCF
Kubernetes API reference — Service — CNCF

Send feedback

Tell us if this tool helped, report a problem, or suggest a tool. Only the message you type is sent — never the input you used in the tool.

Was this tool useful?

Prefer to write to us directly? See the contact page.

Try it

Supported formats

Privacy

How it works

Methodology

Usage

Examples

Node web service

Limitations

What the generated manifest includes

Frequently asked questions

Sources

Related tools

Related guides

Related references

Related concepts

Send feedback

Your consent choices