Delete legacy proxy path

[nikhiljindal]

We right now have two different URL paths in the v1 API for proxying to a pod:

/api/v1/proxy/namespaces/{namespaces}/pods/{name}/{path:*}
/api/v1/namespaces/{namespaces}/pods/{name}/proxy/{path:*}

This is because, we're in the process of moving towards using subresources (the second URL), but haven't deleted the legacy path yet (the first one).

This is to keep track of deleting the legacy proxy path.

[nikhiljindal]

cc @smarterclayton @bgrant0607

[smarterclayton]

The service proxy needs to be moved, @csrwng either knows which issue it is or should be able to create the issue if it doesn't exist

[bgrant0607]

#10038

[lavalamp]

We need:

• Make sure the "new" way works for all resources (services, pods, nodes) (I don't think this is true for 1.1)
• Add to release notes that people need to transition while running 1.2 because it's going away for 1.3
• Actually remove it after 1.2 branch is cut.

[liggitt]

subresource proxying is still in progress for nodes and services:
#18010
#17493

those PRs are pending API approval (and only because the proxy options are considered an API type, despite only containing a path), but are ready otherwise

[lavalamp]

And we won't ever be able to remove the old way from the current API. Only from the new APIs.

[smarterclayton]

Depends. We could certainly age out API patterns with sufficient lead time. It just may not be worth it.

[lavalamp]

I will kick this to the next release once #17493 merges.

[mbohlool]

I think this had sufficient lead. It creates confusion for generated clients to have both connect and proxy in API. I am going to remove proxy as it is deprecated in 1.2

[k8s-github-robot]

[MILESTONENOTIFIER] Milestone Removed

@mbohlool @nikhiljindal

Important: This issue was missing labels required for the v1.9 milestone for more than 3 days:

priority: Must specify exactly one of priority/critical-urgent, priority/important-longterm or priority/important-soon.

Help

• Additional instructions
• Commands for setting labels

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[liggitt]

fixed by #59884