Skip to content

Revert "loadbalancer: Keep non-serving terminating backends"#41199

Closed
jrife wants to merge 1 commit intocilium:mainfrom
jrife:jrife/revert
Closed

Revert "loadbalancer: Keep non-serving terminating backends"#41199
jrife wants to merge 1 commit intocilium:mainfrom
jrife:jrife/revert

Conversation

@jrife
Copy link
Copy Markdown
Contributor

@jrife jrife commented Aug 15, 2025

This reverts commit 6f41c98.

Related: #41194

ci-ginkgo has been failing consistently and it seems to have started with this commit.

This reverts commit 6f41c98.

Related: cilium#41194
Signed-off-by: Jordan Rife <jrife@google.com>
@maintainer-s-little-helper maintainer-s-little-helper bot added the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Aug 15, 2025
@jrife
Copy link
Copy Markdown
Contributor Author

jrife commented Aug 15, 2025

/test

@jrife jrife marked this pull request as ready for review August 15, 2025 23:40
@jrife jrife requested review from a team as code owners August 15, 2025 23:40
@giorio94 giorio94 added release-note/misc This PR makes changes that have no direct user impact. area/loadbalancing Impacts load-balancing and Kubernetes service implementations labels Aug 18, 2025
@maintainer-s-little-helper maintainer-s-little-helper bot removed the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Aug 18, 2025
@giorio94 giorio94 enabled auto-merge August 18, 2025 07:14
@joamaki
Copy link
Copy Markdown
Contributor

joamaki commented Aug 18, 2025

I still don't see any connection whatsoever with the commit and the failing test (the failing test doesn't involve terminating endpoints). I'll rerun the ginkgo test a few more times here with the revert to see if it can be triggered without this commit.

EDIT: The one potential problem could be that we're seeing endpoints without conditions leading them to be quarantined and on agent restart we're picking up this quarantined state that is retained until backend is health checked (which only happens when you have a health checker, which you don't in these tests). We can remove the restoration of the quarantined state as now we default to unhealthy if a health checker is registered. To test if this is the case I opened #41234 to just ignore endpoints that have no conditions and thus won't get quarantined and will do few runs of ginkgo tests there.

Copy link
Copy Markdown
Contributor

@joamaki joamaki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's wait for results from #41234 first.

@joamaki
Copy link
Copy Markdown
Contributor

joamaki commented Aug 18, 2025

#41234 solved the flakyness. Closing this one.

@joamaki joamaki closed this Aug 18, 2025
auto-merge was automatically disabled August 18, 2025 13:49

Pull request was closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/loadbalancing Impacts load-balancing and Kubernetes service implementations release-note/misc This PR makes changes that have no direct user impact.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants