Support new `/meta/proxy` process

[richard-cox]

RFD: https://github.com/SUSE/rancher-architecture/pull/41

Notes

• The existing node driver + /meta/proxy headers will continue to work

Tasks

• Ensure [RFE] Proxy HTTP requests via Rancher rancher#43315 is covered
  • It's likely some parts like CA / trust unsigned won't yet be included. If so we need to make this an epic and spin out some issue
• Create a library / helper to exercise /meta/proxy endpoint
  • Given this will be used in r/d it shouldn't just be extension based
  • Includes replacing / updating docs at https://extensions.rancher.io/extensions/next/provisioning/node-driver/proxying
• Create a library / helper to manage ProxyEndpoint CRDs
  • More orientated to make it easy for extensions to bootstrap env specific domains in crd
  • TBD - they could just use existing / future store extension library
• Use new process for current usages of /meta/proxy
  • TBD
  • if not, deprecate r/d code with comments
• Use new process for new usages of /meta/proxy
  • Ensure we have docs / process in place
• Document library used to support meta/proxy world
  • This is the supportable layer, not the root api requests, so we need docs on extension site
  • Add link to new docs, replacing existing content, at https://extensions.rancher.io/internal/code-base-works/machine-drivers#api-calls

2.15.0 lo-bar

• no extension libraries
• CAPA extension uses /meta/proxy directly
• Either v2prov ec2 node driver exists with aws domain whitelist, or new ProxyEndpoint CR exists containing aws domains in allow list

2.16.0 minumum

• all libraries + other items

[richard-cox]

This is required for the v2prov CAPI work, and also some external partners have shown interest

[eva-vashkevich]

Hi @richard-cox is this ready to be worked on? Based on the status of BE tickets, it seems like it is still backend blocked?

[richard-cox]

@eva-vashkevich We can work on most of this without the pending BE changes (i.e. everything except the first point). Probably requires some discussions before starting though, just so everyone is aligned

[aalves08]

@richard-cox @eva-vashkevich we should all get together look into the details for this 🙏 in the meantime I'll put this as priority/0. Feel free to change if you disagree

[moio]

Create a library / helper to manage ProxyEndpoint CRDs

Could this be a resource installed by Helm charts with UI Extensions?