[release-1.28] Bump konnectivity-client to v0.28.5

[jkh52]

What type of PR is this?

/kind bug

What this PR does / why we need it:

• apiserver
  • konnectivity-client: guard duplicate close (konnectivity-client: code cleanup. kubernetes-sigs/apiserver-network-proxy#456)
• konnectivity-server
  • error propogation fix (fix: error propagation in http-connect mode kubernetes-sigs/apiserver-network-proxy#475)
  • change --delete-existing-uds-file default to true (proxy-server: change --delete-existing-uds-file default to true. kubernetes-sigs/apiserver-network-proxy#498)
  • fix frontend_write_duration_seconds metric (fix: metric frontend_write_duration_seconds has wrong value kubernetes-sigs/apiserver-network-proxy#511)
• konnectivity-agent
  • smarter readiness check (agent: smarter readiness check kubernetes-sigs/apiserver-network-proxy#485)
• konnectivity-server and konnectivity-agent:
  • make client libs consistent ([release-0.28] Bump kubernetes deps to v1.28.5 kubernetes-sigs/apiserver-network-proxy#551)
  • use golang 1.20
  • CVE mitigations
    • Update golang.org/x/net to v0.17.0 kubernetes-sigs/apiserver-network-proxy#533
    • Backport CVE fixes to release-0.28 kubernetes-sigs/apiserver-network-proxy#540
    • [0.28] [CVE-2024-24786] Bump github.com/golang/protobuf v1.5.4, google.golang.org/protobuf v1.33.0 kubernetes-sigs/apiserver-network-proxy#593
  • see Full delta

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

This cherry pick PR is for a release branch and has not yet been approved by Release Managers.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved (/lgtm + /approve) by the relevant OWNERS.

If you didn't cherry-pick this change to all supported release branches, please leave a comment describing why other cherry-picks are not needed to speed up the review process.

If you're not sure is it required to cherry-pick this change to all supported release branches, please consult the cherry-pick guidelines document.

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.

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jkh52
Once this PR has been reviewed and has the lgtm label, please assign dims, sttts for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS
• cluster/gce/OWNERS
• hack/OWNERS
• staging/src/k8s.io/apiextensions-apiserver/OWNERS
• staging/src/k8s.io/apiserver/OWNERS
• staging/src/k8s.io/cloud-provider/OWNERS
• staging/src/k8s.io/controller-manager/OWNERS
• staging/src/k8s.io/kube-aggregator/OWNERS
• staging/src/k8s.io/kube-controller-manager/OWNERS
• staging/src/k8s.io/kubelet/OWNERS
• staging/src/k8s.io/legacy-cloud-providers/OWNERS
• staging/src/k8s.io/pod-security-admission/OWNERS
• staging/src/k8s.io/sample-apiserver/OWNERS
• vendor/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[cici37]

/remove-sig api-machinery

[jkh52]

/retest

[jkh52]

/assign @cheftako

[k8s-ci-robot]

@jkh52: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubernetes-e2e-kind-cloud-provider-loadbalancer	0d6a360	link	false	/test pull-kubernetes-e2e-kind-cloud-provider-loadbalancer

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[aojea]

/test pull-kubernetes-e2e-kind-cloud-provider-loadbalance

this should run only on master :/