KA-R002: Missing readiness probe
Warning Reliability
Why This Matters
The container does not define a readinessProbe. Without a readiness probe, Kubernetes may route traffic to the container before it is ready to handle requests, causing client-facing errors during startup and rollouts.
How to Fix
Add a readinessProbe to the container spec
Before (incorrect)
containers:
- name: app
image: myapp:1.0 After (correct)
containers:
- name: app
image: myapp:1.0
readinessProbe:
httpGet:
path: /ready
port: 8080
initialDelaySeconds: 5
periodSeconds: 10 Rule Details
- Rule Code
- KA-R002
- Severity
- Warning
- Category
- Reliability