[Solved] What is wrong with this liveness probe configuration? livenessProbe: tcpSocket: port: "eighty" initialDelaySeconds: 5 | Kubernetes

Kubernetes - Health Checks and Probes

What is wrong with this liveness probe configuration?

livenessProbe:
  tcpSocket:
    port: "eighty"
  initialDelaySeconds: 5

AtcpSocket probe does not support port specification

BinitialDelaySeconds cannot be less than 10

CThe port value should be an integer, not a string

DThe livenessProbe must use httpGet instead of tcpSocket

Step-by-Step Solution

Solution:

Step 1: Check port type
The port field in tcpSocket must be an integer or named port, not a string representing a word.
Step 2: Validate other fields
initialDelaySeconds can be any non-negative integer; 5 is valid.
Step 3: Confirm tcpSocket usage
tcpSocket supports port specification; httpGet is not mandatory.
Final Answer:
The port value should be an integer, not a string -> Option C
Quick Check:
Port must be integer or named port, not string [OK]

Quick Trick: Port must be integer or named port, not string [OK]

Common Mistakes:

Master "Health Checks and Probes" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

More Kubernetes Quizzes

What is wrong with this liveness probe configuration?