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
egress_selector: prevent goroutines leak on connect() step. #114012
Conversation
/retest |
/assign @liggitt @andrewsykim |
/lgtm this makes sense to me as a backstop |
/triage accepted |
What's the reason for not backporting this to release-1.23? |
there are refactors of dialing code that mean the backport doesn't apply cleanly. See #113862 (comment) |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jkh52, liggitt, saschagrunert 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:
Cherry pick #113486 to release-1.25
I want this because:
dial_failure_count
(forStageConnect
)Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: