What is the difference between CPU requests and limits?

CPU request is the guaranteed minimum compute allocated by the node scheduler. CPU limit is the hard ceiling; if a container exceeds its limit, it is throttled (not killed).

What happens if a container exceeds its Memory limit?

Unlike CPU (which throttles), exceeding a memory limit causes the Linux kernel to terminate the container process immediately with an OOMKilled (Exit Code 137) error.

How do I deploy the generated manifest?

Save the downloaded YAML file and apply it directly to your cluster using `kubectl apply -f manifest.yaml`.

Back to Dev Tools

100% Client-side & Private Sandbox

Kubernetes Manifest Studio

DevOps & CI/CD

Visual manifest generator for Kubernetes Deployments, Services, TLS Ingress, and Autoscalers with workload resource sizing.

1. Workload Identity & Pods

App Name

Namespace

Container Image

Container Port

Initial Replicas

2. Resource Sizing & Limits

CPU Request / Limit

Memory Request / Limit

3. Networking, Ingress & Autoscaler

Service Type

Generate Ingress (Nginx & TLS)

Route HTTP traffic from external domain

Domain Hostname

cert-manager Let's Encrypt TLS

Horizontal Pod Autoscaler (HPA)

Scale pod count automatically based on CPU usage

Min Pods

Max Pods

Target CPU %

k8s.yaml (Multi-Document)KUBERNETES

apiVersion: v1
kind: Namespace
metadata:
  name: production
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: api-service-config
  namespace: production
data:
  NODE_ENV: "production"
  LOG_LEVEL: "info"
  PORT: "8080"
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: api-service
  namespace: production
  labels:
    app.kubernetes.io/name: api-service
    app.kubernetes.io/part-of: sprintkit
spec:
  replicas: 3
  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 0
  selector:
    matchLabels:
      app: api-service
  template:
    metadata:
      labels:
        app: api-service
    spec:
      securityContext:
        runAsNonRoot: true
        runAsUser: 10001
        fsGroup: 10001
      containers:
        - name: api-service
          image: ghcr.io/org/api-service:v1.2.0
          imagePullPolicy: IfNotPresent
          ports:
            - containerPort: 8080
              name: http
          envFrom:
            - configMapRef:
                name: api-service-config
          resources:
            requests:
              cpu: 200m
              memory: 256Mi
            limits:
              cpu: 500m
              memory: 512Mi
          livenessProbe:
            httpGet:
              path: /healthz
              port: http
            initialDelaySeconds: 15
            periodSeconds: 10
            timeoutSeconds: 3
            failureThreshold: 3
          readinessProbe:
            httpGet:
              path: /healthz
              port: http
            initialDelaySeconds: 5
            periodSeconds: 5
            timeoutSeconds: 2
            failureThreshold: 2
---
apiVersion: v1
kind: Service
metadata:
  name: api-service-svc
  namespace: production
  labels:
    app: api-service
spec:
  type: ClusterIP
  selector:
    app: api-service
  ports:
    - name: http
      port: 80
      targetPort: http
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: api-service-ingress
  namespace: production
  annotations:
    kubernetes.io/ingress.class: nginx
    cert-manager.io/cluster-issuer: letsencrypt-prod
spec:
  tls:
    - hosts:
        - api.example.com
      secretName: api-service-tls-cert
  rules:
    - host: api.example.com
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: api-service-svc
                port:
                  number: 80
---
apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:
  name: api-service-hpa
  namespace: production
spec:
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: api-service
  minReplicas: 2
  maxReplicas: 8
  metrics:
    - type: Resource
      resource:
        name: cpu
        target:
          type: Utilization
          averageUtilization: 75

Ready for `kubectl apply -f k8s.yaml`136 lines · 2858 chars

Kubernetes Manifest Studio

Unified Kubernetes YAML Generator & Pod Sizing Studio

How to Generate Kubernetes Manifests

Configure App & Workload Sizing

Configure Networking & TLS Ingress

Add Health Probes & Auto-Scaling

Kubernetes Studio Capabilities

Automated Resource Sizing

Ingress with cert-manager TLS

Single Unified Multi-Doc YAML

Kubernetes Production Best Practices

Frequently Asked Questions

Related Agile & Developer Tools