hard20 pts · first answer countskubernetesgraceful-shutdown

Errors during every rollout

Your app handles SIGTERM correctly and stops accepting connections right away. Still, clients see a few 502 errors at every rollout. What is the most likely cause and fix?

A.The readiness probe period is too long; set it to 1 second and the errors disappear.B.Endpoint removal reaches load balancers and kube-proxy asynchronously, so traffic still arrives after SIGTERM; add a short preStop sleep (or delay shutdown) so the Pod keeps serving until routing is updated.C.Kubernetes sends SIGKILL before SIGTERM; increase terminationGracePeriodSeconds to 300.D.The Service must be type LoadBalancer for graceful shutdown to work.

Discussion 0

Join free to post in the discussion.

Errors during every rollout

Discussion 0

Related questions