Readiness probe concept in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a readiness probe that checks HTTP path '/ready'.

Kubernetes

readinessProbe:
  httpGet:
    path: [1]
    port: 8080

Drag options to blanks, or click blank then click option'

A/status

B/health

C/ready

D/check

Attempts:

3 left

💡 Hint

Common Mistakes

Using a liveness probe path instead of readiness probe path.

Using a path that does not exist in the container.

The readiness probe uses the HTTP path '/ready' to check if the container is ready to receive traffic.

2fill in blank

medium

Complete the code to set the readiness probe initial delay to 5 seconds.

Kubernetes

readinessProbe:
  initialDelaySeconds: [1]

Drag options to blanks, or click blank then click option'

A5

B0

C10

D15

Attempts:

3 left

💡 Hint

Common Mistakes

Setting initialDelaySeconds to 0 which may cause premature checks.

Using a very high delay causing slow readiness detection.

The initialDelaySeconds field sets how long Kubernetes waits before starting readiness checks. Here it is set to 5 seconds.

3fill in blank

hard

Fix the error in the readiness probe port number (should be 8080).

Kubernetes

readinessProbe:
  httpGet:
    path: /ready
    port: [1]

Drag options to blanks, or click blank then click option'

A80

B8080

C443

D3000

Attempts:

3 left

💡 Hint

Common Mistakes

Using default HTTP port 80 when the app listens on 8080.

Using HTTPS port 443 incorrectly.

The readiness probe must use the correct port 8080 where the container serves readiness requests.

4fill in blank

hard

Fill both blanks to set readiness probe timeout to 3 seconds and period to 10 seconds.

Kubernetes

readinessProbe:
  timeoutSeconds: [1]
  periodSeconds: [2]

Drag options to blanks, or click blank then click option'

A3

B5

C10

D15

Attempts:

3 left

💡 Hint

Common Mistakes

Setting timeoutSeconds longer than periodSeconds.

Using very high values causing slow detection.

timeoutSeconds is set to 3 to limit probe wait time, and periodSeconds is set to 10 to check every 10 seconds.

5fill in blank

hard

Fill all three blanks to define a readiness probe with exec command 'cat /tmp/ready', initial delay 5, and failure threshold 3.

Kubernetes

readinessProbe:
  exec:
    command: [[1]]
  initialDelaySeconds: [2]
  failureThreshold: [3]

Drag options to blanks, or click blank then click option'

Acat /tmp/ready

B5

C3

Dls /tmp

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong exec command that does not check readiness.

Setting failureThreshold too low causing false failures.

The exec command checks the file '/tmp/ready' to confirm readiness. Initial delay is 5 seconds, and failure threshold is 3 retries.