Skip to content

EPP should gracefully rollout and drain #548

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Tracked by #493
smarterclayton opened this issue Mar 20, 2025 · 0 comments · Fixed by #614
Closed
Tracked by #493

EPP should gracefully rollout and drain #548

smarterclayton opened this issue Mar 20, 2025 · 0 comments · Fixed by #614
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@smarterclayton
Copy link
Contributor

The EPP is part of an active-active system and should have hitless rollouts.

Any particular EPP must drain during shutdown all requests such that the longest running active request completes as long as it is on the critical path for startup (future changes such as splitting the algorithm or queueing may reduce the delay for the EPP, but not the need).

Tested in a GKE specific context here, I would expect all integrating gateways to understand this is part of the gateway protocol when consuming the EPP directly.

Image

@smarterclayton smarterclayton added the kind/bug Categorizes issue or PR as related to a bug. label Mar 20, 2025
@ahg-g ahg-g mentioned this issue Mar 25, 2025
14 tasks
@kfswain kfswain self-assigned this Mar 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants