Bump konnectivity-client to v0.0.28

[cheftako]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Bump konnectivity network proxy to v0.0.28.
Includes a fix to ensure the KAS calls Close() on the egress connection.
Pulls in updates ANP binary fixes (https://github.com/kubernetes-sigs/apiserver-network-proxy/commits/v0.0.28)

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.:

[cheftako]

/priority important-soon
/assign @Jefftree @andrewsykim

[andrewsykim]

/lgtm

For the record, @rata and I are still investigating some remaining leaks in kubernetes-sigs/apiserver-network-proxy#276, but given this fixes a significant goroutine leak (specifically when proxy server restarts) and seems safe/obvious I think we should still backport it.

[k8s-triage-robot]

Unknown CLA label state. Rechecking for CLA labels.

Send feedback to sig-contributor-experience at kubernetes/community.

/check-cla
/easycla

[rata]

@andrewsykim for other leaks (like when we upgraded to 0.0.27 was also for a leak), we back-ported the changes to all supported versions (it was requested by the release team to do it for all branches at the same time). I don't think anyone will oppose to do the same now, once this is merged :)

[andrewsykim]

/assign @liggitt

[liggitt]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cheftako, 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:

• OWNERS [liggitt]
• staging/src/k8s.io/legacy-cloud-providers/OWNERS [cheftako,liggitt]

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

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

[rata]

For the record, I can confirm this PR fixes too the issue when proxy-server is down for a few minutes. With this PR, when proxy-server starts again, the number of proxy connections established from the apiserver is the expected. Without this PR, the number of connections grows as the proxy-server is down for more time.

[fedebongio]

/triage accepted