Skip to content
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

[release-v3.27] Auto pick #8438: proxy - syncer must not count not-ready endpoints #8460

Conversation

tomastigera
Copy link
Contributor

Cherry pick of #8438 on release-v3.27.

#8438: proxy - syncer must not count not-ready endpoints

Original PR Body below

We include terminating eps in the eps list so that we can prevent conntrack clean up, but they are not written into the backend map and so they should not be reflected in the backends count.

Test that Terminating is propagated through proxy frontend. Test in FV that proxy removes the terminating backend from the NAT table.

refs #8423

Description

Related issues/PRs

Todos

  • Tests
  • Documentation
  • Release note

Release Note

ebpf: fixes possible holes in the list NAT backends if there is a terminating pod.

Reminder for the reviewer

Make sure that this PR has the correct labels and milestone set.

Every PR needs one docs-* label.

  • docs-pr-required: This change requires a change to the documentation that has not been completed yet.
  • docs-completed: This change has all necessary documentation completed.
  • docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

  • release-note-required: This PR has user-facing changes. Most PRs should have this label.
  • release-note-not-required: This PR has no user-facing changes.

Other optional labels:

  • cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
  • needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

We include terminating eps in the eps list so that we can prevent
conntrack clean up, but they are not written into the backend map and so
they should not be reflected in the backends count.

Test that Terminating is propagated through proxy frontend.
Test in FV that proxy removes the terminating backend from the NAT
table.

refs projectcalico#8423
@tomastigera tomastigera requested a review from a team as a code owner January 29, 2024 20:30
@tomastigera tomastigera added release-note-required Change has user-facing impact (no matter how small) cherry-pick-candidate docs-not-required Docs not required for this change labels Jan 29, 2024
@marvin-tigera marvin-tigera added this to the Calico v3.27.1 milestone Jan 29, 2024
@tomastigera
Copy link
Contributor Author

/merge-when-ready

@marvin-tigera
Copy link
Contributor

OK, I will merge the pull request when it's ready, leave the commits as is when I merge it, and leave the branch after I've merged it.

@marvin-tigera marvin-tigera merged commit 33de95e into projectcalico:release-v3.27 Jan 30, 2024
2 checks passed
@tomastigera tomastigera deleted the auto-pick-of-#8438-release-v3.27 branch January 31, 2024 01:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick-candidate docs-not-required Docs not required for this change merge-when-ready release-note-required Change has user-facing impact (no matter how small)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants