Generate Kubernetes YAML manifests for Deployments, Services, ConfigMaps, Ingress rules, and HPAs.
apiVersion: apps/v1
kind: Deployment
metadata:
name: my-app
namespace: default
labels:
app: my-app
spec:
replicas: 2
selector:
matchLabels:
app: my-app
template:
metadata:
labels:
app: my-app
spec:
containers:
- name: my-app
image: myapp:latest
ports:
- containerPort: 3000
resources:
requests:
cpu: 100m
memory: 128Mi
limits:
cpu: 500m
memory: 512Mi
env:
- name: NODE_ENV
value: "production"
livenessProbe:
httpGet:
path: /healthz
port: 3000
initialDelaySeconds: 15
periodSeconds: 20
readinessProbe:
httpGet:
path: /ready
port: 3000
initialDelaySeconds: 5
periodSeconds: 10Kubernetes resources are defined as YAML manifests and applied with <code>kubectl apply -f</code>. A Deployment manages a set of replicated Pods. A Service exposes those Pods on a stable IP or DNS name. A ConfigMap stores non-secret configuration data. An Ingress routes external HTTP traffic to internal Services. An HPA automatically scales Deployment replicas based on CPU or memory usage.
Select a resource type from the tabs at the top. Fill in the fields for that resource, then copy the generated YAML. Use the All Resources tab to generate all five manifests at once as a single multi-document YAML file separated by <code>---</code> delimiters.
Resource requests define the minimum CPU and memory a container needs for scheduling. Limits cap the maximum a container can consume. Setting requests without limits is the most common production pattern - it guarantees scheduling headroom while allowing bursting. The HPA requires metrics-server to be installed in the cluster. Ingress rules require an Ingress controller such as nginx-ingress or Traefik.