-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
bump konnectivity-client@v0.0.30 #108437
bump konnectivity-client@v0.0.30 #108437
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/triage accepted |
commented on kubernetes-sigs/apiserver-network-proxy#337, but is there a test demonstrating this resolves the issue and ensuring it won't regress in the future? |
There is a regression test added for the first goroutine leak here kubernetes-sigs/apiserver-network-proxy#336. And a tracking issue for it here kubernetes-sigs/apiserver-network-proxy#333 The second one is tricky to test because it's hard to trigger the race condition in a test. |
To be clear, there are no unit tests demonstrating this fix, but it has been manually validated by myself and @rata, see kubernetes-sigs/apiserver-network-proxy#276 (comment) |
kubernetes-sigs/apiserver-network-proxy#339 isn't in 0.0.29... a v0.0.30 cut and an update here is needed |
I'll update this PR and the other cherry-pick PRs once @cheftako cuts v0.0.30. We may end up delaying v0.0.30 until we have some test coverage for goroutine leaks though. |
Signed-off-by: Andrew Sy Kim <andrewsy@google.com>
a918133
to
00e2225
Compare
/lgtm |
/hold cancel |
/test ? |
@liggitt: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
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. |
Can we also change https://github.com/kubernetes/kubernetes/blob/master/cluster/gce/addons/konnectivity-agent/konnectivity-agent-ds.yaml#L30 and https://github.com/kubernetes/kubernetes/blob/master/cluster/gce/manifests/konnectivity-server.yaml#L23 to ensure we are consistent on the v0.0.30? |
/hold for manifest bump |
Signed-off-by: Andrew Sy Kim <andrewsy@google.com>
Good catch, updated |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andrewsykim, 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 |
/hold cancel |
Signed-off-by: Andrew Sy Kim andrewsy@google.com
What type of PR is this?
/kind bug
What this PR does / why we need it:
Bumps sigs.k8s.io/apiserver-network-proxy/konnectivity-client to v0.0.30, which includes two fixes for goroutine leaks in kube-apiserver:
See kubernetes-sigs/apiserver-network-proxy#276 (comment) for more details on the root cause.
Which issue(s) this PR fixes:
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.: