Adding deprecation notice to the userspace proxy-mode

[perithompson]

This PR adds a deprecation notice for the userspace kube-proxy that needs to be removed, the reasons behind this are documented it #103860

What type of PR is this?

/kind deprecation

What this PR does / why we need it:

Userspace proxy has essentially become unsupported in kube-proxy and recently sig-network has decided to remove the userspace linux and windows proxies from kubernetes core. As part of this work we need to add a deprecation warning when running with userspace proxy that this is now deprecated and another proxy mode should be used.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

related to
#103860

Does this PR introduce a user-facing change?

A deprecation notice has been added when using the kube-proxy Userspace proxier, which will be removed in v1.25. (#103860)

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

[k8s-ci-robot]

@perithompson: Adding the "do-not-merge/release-note-label-needed" label and removing any existing "release-note-none" label because there is a "kind/deprecation" label on the 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.

[k8s-ci-robot]

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

[perithompson]

@jayunit100 started this here, not sure if I can mark the flag as deprecated because its only one option, not the whole flag

[perithompson]

/cc @jayunit100
/sig network

[perithompson]

@jayunit100 PTAL and let me know if you wanted more comments anywhere else?

[khenidak]

/assign @khenidak

Please add a release note so we can merge this one.

[khenidak]

/lgtm
/approve

[khenidak]

Thanks for this.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: khenidak, perithompson

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:

• cmd/kube-proxy/OWNERS [khenidak]

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

[aojea]

/cc @danwinship
Thanks