Health and capacity practice

Opening your lesson

Readiness decides whether a Pod should receive Service traffic. Liveness asks whether a container needs a restart. A resource request tells the scheduler how much capacity a container needs. A resource limit bounds how much it may use at runtime. Start a resource incident with its status and events. Pending means the Pod has not reached a runnable placement; requests, node selection or storage may block it.

Apply those boundaries to fresh fixtures. Inspect the requested name, namespace, path and value before reusing a command. The tasks mix earlier operations and include nearby wrong targets, so preserve unrelated work. Choose any supported approach that produces the complete requested state; the checker evaluates the result rather than a recorded command sequence.

printf '%s' 'apiVersion: "apps/v1"
kind: "Deployment"
metadata:
  name: "cobalt-925"
spec:
  replicas: 2
  selector:
    matchLabels:
      app: "cobalt-925"
  template:
    metadata:
      labels:
        app: "cobalt-925"
    spec:
      containers:
        - name: "cobalt-925"
          image: "nginx:1.27"
          ports:
            - containerPort: 80
          readinessProbe:
            httpGet:
              path: "/health"
              port: 80
            initialDelaySeconds: 2
            periodSeconds: 5
' > 'workload.yaml'
kubectl apply -f workload.yaml

A worked pattern on separate practice data.

Choose your character

Your Work Gym account