Pass endpointslice fencing on ingress-nginx provider#13290
Merged
traefiker merged 2 commits intoJun 9, 2026
Merged
Conversation
Learloj
changed the title
Contributor
|
Hey @Learloj, |
gndz07
changed the title
gndz07
force-pushed
the
bugfix/13287-fix-ingress-nginx-endpointslice-fencing
branch
3 times, most recently
from
June 8, 2026 15:33
6384ec5 to
a8869f8
Compare
gndz07
force-pushed
the
bugfix/13287-fix-ingress-nginx-endpointslice-fencing
branch
from
June 8, 2026 15:33
a8869f8 to
965daee
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Fixes when endpointslice is updated, marking an endpoint as
ready: falseandterminating: true, Traefik's ingress-nginx provider marks the server as fenced and stops sending new traffic to it.Motivation
We want our pods to be able to gracefully terminate, and to do so, they should stop receiving new requests and be able to handle existing requests, until done and then stop. Right now, they get traffic when they are in Terminating state, until they are fully stopped, which sometimes results in requests being sent to a pod which is already stopped, resulting in HTTP timeouts towards the client.
More
Additional Notes
Fixes #13287