You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Envoy ShutdownManager, the first thing that happens is we tell Envoy to fail its healthchecks which causes the container to fail its readiness probe and start to drain connections.
It's possible that the initial call will fail and Envoy never starts to drain connections. If this occurs then the pod will wait it's total grace period seconds before terminating.
A best-effort could be applied to retry the healthcheck fail call if it doesn't succeed on the first attempt.
…hcheck fail
The call in the shutdown-manager to intitiate the Envoy healthcheck fail HTTP request
did not retry in the event that the call fails. Adds the client-go retry.OnError method
which takes a backoff object allowing for a retry with backoff in the event the request
fails.
Fixesprojectcontour#2262
Signed-off-by: Steve Sloka <[email protected]>
…hcheck fail (#3136)
The call in the shutdown-manager to intitiate the Envoy healthcheck fail HTTP request
did not retry in the event that the call fails. Adds the client-go retry.OnError method
which takes a backoff object allowing for a retry with backoff in the event the request
fails.
Fixes#2262
Signed-off-by: Steve Sloka <[email protected]>
In the Envoy ShutdownManager, the first thing that happens is we tell Envoy to fail its healthchecks which causes the container to fail its readiness probe and start to drain connections.
It's possible that the initial call will fail and Envoy never starts to drain connections. If this occurs then the pod will wait it's total grace period seconds before terminating.
A best-effort could be applied to retry the healthcheck fail call if it doesn't succeed on the first attempt.
Originally posted by @jpeach in #2227 (comment)
The text was updated successfully, but these errors were encountered: