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

[1.22] cni: properly cleanup completed pods (#51713) #51734

Merged
merged 1 commit into from
Jun 26, 2024

Conversation

howardjohn
Copy link
Member

Fixes #51727

* cni: properly cleanup completed pods

Followup to istio#51429.

When a pod is moved to terminal stage, we call RemovePodFromMesh. This
has a variety of cleanup steps, and aborts early if any fail.

Because the pod is terminated, we will fail to cleanup the in-pod rules.
This is OK! The pod is terminated anyways. But with the current logic,
this also means we do not send ztunnel the removed message, and it will
leak proxy instances.

Additionally, this does a variety of logging cleanups so that we
consistently format messages and always show which pod we are acting on.

* Address comments

(cherry picked from commit 760ad26)
@howardjohn howardjohn requested a review from a team as a code owner June 26, 2024 15:18
@howardjohn howardjohn added the release-notes-none Indicates a PR that does not require release notes. label Jun 26, 2024
@istio-testing istio-testing added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jun 26, 2024
@howardjohn howardjohn changed the title cni: properly cleanup completed pods (#51713) [1.22] cni: properly cleanup completed pods (#51713) Jun 26, 2024
@istio-testing istio-testing merged commit b210c2b into istio:release-1.22 Jun 26, 2024
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-notes-none Indicates a PR that does not require release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants