Challenge - Pod YAML

Write a Pod YAML with specific labels.

Challenge: a production-ready pod

A good pod definition is more than just an image. In this challenge you'll combine the intermediate pod best practices in one definition:

Meaningful labels
Resource requests and limits
Readiness and liveness checks
Settings from a ConfigMap, the password from a Secret

resources:
  requests: {cpu: 100m, memory: 128Mi}
  limits:   {cpu: 500m, memory: 256Mi}
readinessProbe:
  httpGet: {path: /saglik, port: 8080}
livenessProbe:
  httpGet: {path: /saglik, port: 8080}
  initialDelaySeconds: 10

Exercise The pod's container

Write a pod YAML: name api, label app: api; container named api, image api:1.0; resources.requests cpu: 100m, memory: 128Mi; resources.limits memory: 256Mi.

Show example solution

apiVersion: v1
kind: Pod
metadata:
  name: api
  labels:
    app: api
spec:
  containers:
    - name: api
      image: api:1.0
      resources:
        requests:
          cpu: 100m
          memory: 128Mi
        limits:
          memory: 256Mi

Exercise Health checks

Write the health checks for the same container (starting with readinessProbe:): readinessProbe checks /saglik on port 8080 with httpGet; livenessProbe uses the same path and port with initialDelaySeconds: 10.

Show example solution

readinessProbe:
  httpGet:
    path: /saglik
    port: 8080
livenessProbe:
  httpGet:
    path: /saglik
    port: 8080
  initialDelaySeconds: 10

Test yourself

For a pod without requests, what does the scheduler assume?
- Zero resources; the pod may be placed even on a full node
- All of the node's resources
- 1 CPU and 1 GiB
- The pod is rejected
Show answer

Zero resources; the pod may be placed even on a full node — With no requests (and no LimitRange), there's no resource guarantee either.

Specify the guaranteed resources.

resources:
  ____:
    cpu: 100m
    memory: 128Mi

Show answer

resources:
  requests:
    cpu: 100m
    memory: 128Mi

Match.

requests

Scheduling guarantee
limits

Ceiling that can't be exceeded
readinessProbe

Traffic gate
livenessProbe

Catches hangs

Next lesson: Challenge - Deployment

We Are Enhancing Your Experience

Cookie Preferences

Strictly Necessary Cookies

Analytical Cookies