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 to v0.0.35 in release-1.25 #114929
Bump Konnectivity to v0.0.35 in release-1.25 #114929
Conversation
./hack/pin-dependency.sh sigs.k8s.io/apiserver-network-proxy/konnectivity-client v0.0.35 ./hack/update-codegen.sh ./hack/update-vendor.sh Manual adjustments: vendor/modules.txt cluster/gce/addons/konnectivity-agent/konnectivity-agent-ds.yaml cluster/gce/manifests/konnectivity-server.yaml
/cc @liggitt |
/priority important-soon |
LGTM label has been added. Git tree hash: e60d07c74bc8752119bc522e5e4effb9b7b38534
|
/lgtm |
cc @kubernetes/release-managers |
/triage accepted |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, 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 |
/triage accepted |
/triage accepted |
1 similar comment
/triage accepted |
/remove-triage accepted |
/triage accepted |
Bump Konnectivity to v0.0.35 in release-1.25
What type of PR is this?
/kind feature
What this PR does / why we need it:
Supports new metrics, logging improvements, and trivial fixes only (no major changes).
Which issue(s) this PR fixes:
Special notes for your reviewer:
konnectivity-client (apiserver): This bumps Konnectivity to v0.0.35 in release-1.25, but unlike #114927 (which merges cleanly), this is a by-hand "repeat" of #114789 only, in order to resolve conflicts. After this, I would send separate PR to register new metrics. Doing this more conservatively in release-1.25 makes sense (but if reviewers prefer to be in lockstep, I could add commits for the other two PRs here).
proxy-server and proxy-agent: v0.0.35 consistently with #114927. (New metrics, logging improvements, and trivial fixes only (no major changes).
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: