[EPIC] Support CAPI Providers in Provisioning v2

[richard-cox]

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

Tasks

• [v2.14] Handle v2prov CAPI clusters provisioned outside of the UI #16679
• [v2.15] Handle v2prov CAPI clusters provisioned outside of the UI #16636
• Handle install, setup and management of v2prov CAPI Providers + their UI Extensions #16539
  • [RFE] Allow users with the clusters-create role to view capiprovider resource rancher#55167
• Create and Manage clusters via CAPA CAPI Provider #16540
  • Handle CloudCredentials and v2Prov CAPI CAPA clusters #17443
• Create and Manage clusters via vSphere CAPI Provider #16541
• Support new /meta/proxy process #16490
• Edit Yaml Experience
  • Disable editing of YAML for v2prov capi clusters #17679
  • Enable editing of YAML for v2prov capi clusters #17680
• Enhance cluster type selection page #17662
• Create and Manage clusters via BYO CAPI Provider #16542
• Create a process to improve use + management of BYO CAPI provider credentials #16543

General Points to Consider (outside of those in sub-tasks)

• Create a cluster
  • TBD (UX) Do we offer the option to clone an existing template (aka template library)?
    • Future Work
• TBD (BE) What does the UI do for CAPI clusters created outside of v2prov world?
• TBD What happens if the UI edits a cluster that was provisioning by CAPI Turtles using CAPI provider creds?

General

• When will node drivers be deprecated?

[richard-cox]

There are two methods to create/manage machine templates

Method 1: Support providers via a generic ui extension with dynamic cluster create form
Method 2: Support providers via provider specific ui extensions with hardcoded cluster create form

Plus other methods

Method 3: Outside of the GUI (kube api, kube cli, terraform, etc)

Blocked on

• Decision on MVP and UI requirements
  • Method 2 with AWS/EC2 was chosen
• Compatible with or replacement for cloudcredentials (without UX degregation)
  • Affects all methods (1, 2 and 3)
  • Info updated in sub issues (including blockers)
    • Currently CC types - carries on as before
    • BYO providers - process support
• Support for /meta/proxy
  • Info updated in sub issues (including blockers)
  • Affects method 2 only, and for those that don't have a hardcoded proxy (which for node driver like providers i think is only /meta/vsphere)
  • All proxied requests use cloudcredentials for auth to that provider