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-1.24] Bump konnectivity-client to v0.0.36 #115890
[release-1.24] Bump konnectivity-client to v0.0.36 #115890
Conversation
This cherry pick PR is for a release branch and has not yet been approved by Release Managers. To merge this cherry pick, it must first be approved ( AFTER it has been approved by code owners, please leave the following comment on a line by itself, with no leading whitespace: /cc kubernetes/release-managers (This command will request a cherry pick review from Release Managers and should work for all GitHub users, whether they are members of the Kubernetes GitHub organization or not.) For details on the patch release process and schedule, see the Patch Releases page. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign @tallclair |
/triage accepted |
/lgtm |
LGTM label has been added. Git tree hash: 8c91c0cfebe780a7f5b4ced5acaaaaf8a72d8443
|
@jkh52 @tallclair hi, can you please / approve this one? thanks! |
/assign @liggitt |
Friendly ping. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jkh52, liggitt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind bug
What this PR does / why we need it:
This fix addresses memory leaks by improving proxy connection cleanup.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Same as #115599 but for release-1.24 branch.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: