Operators want faster failure detection on a civic chat Pod without flapping on brief blips. Which probe timing approach balances speed and stability?
Select an answer to reveal the explanation.
Short Explanation
Probe timing is like a smoke alarm’s sensitivity dial. Shorter periods catch trouble sooner, but you still want a few failed checks—failureThreshold—before you declare the building on fire. Tune both so real outages show up without flapping on hiccups.
Full Explanation
periodSeconds sets how often kubelet probes; failureThreshold sets how many consecutive failures trigger the probe’s effect (restart for liveness, Endpoints removal for readiness). Combining a reasonable period with a threshold greater than one reduces false positives while still bounding detection latency. Extreme single-failure aggressive settings and zero timeouts amplify flapping; removing probes removes automated protection.