A rolling update of a Spring Boot Deployment causes a brief spike in 502 errors during every deployment
The Deployment uses default rolling update settings and a readinessProbe pointed at /actuator/health/readiness. Diagnose likely causes. Expected reasoning: check initialDelaySeconds on the readiness probe — if it's shorter than the application's actual startup/warm-up time, Kubernetes may start routing traffic to a Pod that reports ready prematurely (or worse, the probe path itself isn't accurately reflecting true readiness, e.g., a connection pool not yet warmed). Also verify maxUnavailable isn't set high enough to remove too many old Pods before enough new ones are confirmed ready, and confi
Ready to master this question?
Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.
Sign in to generate a response