advancedAWS & Kubernetes103 of 107
Newly deployed pods pass readiness checks but clients get 502/503 while old pods work. How do you debug before rolling back?
Tests whether you suspect the readiness probe is checking something too shallow (e.g. just TCP connect) that doesn't reflect actual app readiness -- the app may need more warm-up time (JIT, connection pool init) than the probe accounts for, so it's marked ready before it can actually serve traffic.
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 responseNext Step
←PreviousContinue to Which network, socket and process checks (ss, file descriptors, lingering sockets, port bindings) help you compare healthy and broken pods?→
← Back to all DevOps, Docker & AWS questions