Remove references to userspace proxy

[danwinship]

While belatedly looking at #36675 I saw that we still talk about the userspace proxy in a bunch of places, but it's gone in 1.26 (kubernetes/kubernetes#112133).

I didn't remove static/images/docs/services-userspace-overview.{svg,png} because it's referenced by the translations of service.md too.

/cc @sftim

[netlify]

👷 Deploy Preview for kubernetes-io-vnext-staging processing.

Name	Link
🔨 Latest commit	37ee1e3
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/638f4d6fe284310008c35d18

[sftim]

IMO, this change should land after we merge in main

The proxy modes are now documented in https://kubernetes.io/docs/reference/networking/virtual-ips/

[sftim]

Avoid touching autogenerated files such as content/en/docs/reference/command-line-tools-reference/kube-proxy.md. Those changes will be overwritten during the release process.

/hold
OK to unhold this (unless other grounds have appeared) once that change is omitted.

[sftim]

You might also like to work on #38244 @danwinship

[danwinship]

Avoid touching autogenerated files such as content/en/docs/reference/command-line-tools-reference/kube-proxy.md. Those changes will be overwritten during the release process.

ah, well, I just copied the text from kube-proxy --help so it would hopefully have been overwritten with exactly the same thing, but if it's going to happen automatically anyway, then yay
/hold cancel

[danwinship]

IMO, this change should land after we merge in main

I'm not sure what that means relative to what ends up in the official 1.26 documentation, but note that as of right now, dev-1.26 contains references to something (userspace proxy mode) that doesn't exist in 1.26.

[sftim]

I'm worried that our choices might come down to:

• ship with stale docs about kube-proxy, and fix them after the release
• create a merge conflict that we don't really have time / resources to fix before the release

It'd be nice to find a third option here.

[sftim]

#38242 is about to land. If you rebase on upstream's dev-1.26 then we should be able to get this in the release.

If not, it's not a huge problem because this repo is continously deployed: update the PR to target main, go through code review, and we can get an update out, pronto.

[sftim]

There is also a kernelspace mode - see #38244

[danwinship]

This PR necessarily conflicts with that one (that PR modifies the text immediately before the ### User space proxy mode heading which this PR removes), so one of us will have to rebase

[sftim]

What matters most to me is not provoking a merge conflict for dev-1.26 going into main.
I can add the kernelspace one into the dev-1.26 docs and then, after the v1.26, propose a backport.

[sftim]

Thanks

/approve

[krol3]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 9e78ef58b6beb7118706b18601dad274c37592a1

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: krol3, sftim

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:

• content/en/OWNERS [krol3,sftim]

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

[sftim]

Manually triggering a merge by GitHub as repository is frozen for 1.26 release.