[BUG] Schema Definitions are missing formation for RKE Config on the provisioning cluster

[MbolotSuse]

Rancher Server Setup

• Rancher version: v2.9-head (c9be13b09329bbee60a5f6419d500198f83c44d1
• Installation option (Docker install/Helm Chart): Docker install
• Proxy/Cert Details: N/A

Information about the Cluster

• Kubernetes version: v1.27.10+k3s2
• Cluster Type (Local/Downstream): Local
  • If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): N/A

User Information

• What is the role of the user logged in? (Admin)
  • If custom, define the set of permissions: N/A

Describe the bug The schema definition for the rkeConfig field of the provisioning.cattle.io.cluster object has no-subfields and an incorrect type.

To Reproduce

1. Run rancher/rancher:v2.9-head
2. Retrieve the schemaDefinition for the provisioning cluster ($RANCHER/v1/schemaDefinitions/provisioning.cattle.io.cluster)

Result The response contains the following for the "io.cattle.provisioning.v1.Cluster.spec" definition:

"resourceFields": {
    ...
    "rkeConfig": {
        "type": "string"
    }
},

Expected Result More fields should be present for the rkeConfig object, including the fields identified by kubctl explain clusters.provisioning.cattle.io.spec.rkeConfig:

GROUP:      provisioning.cattle.io
KIND:       Cluster
VERSION:    v1

FIELD: rkeConfig <Object>

DESCRIPTION:
    <empty>
FIELDS:
  additionalManifest    <string>
    <no description>

  chartValues   <Object>
    <no description>

  etcd  <Object>
    <no description>

  etcdSnapshotCreate    <Object>
    <no description>

  etcdSnapshotRestore   <Object>
    <no description>

  infrastructureRef <Object>
    <no description>

  machineGlobalConfig   <Object>
    <no description>

  machinePoolDefaults   <Object>
    <no description>

  machinePools  <[]Object>
    <no description>

  machineSelectorConfig <[]Object>
    <no description>

  machineSelectorFiles  <[]Object>
    <no description>

  networking    <Object>
    <no description>

  provisionGeneration   <integer>
    <no description>

  registries    <Object>
    <no description>

  rotateCertificates    <Object>
    <no description>

  rotateEncryptionKeys  <Object>
    <no description>

  upgradeStrategy   <Object>
    <no description>

Screenshots N/A

Additional context This represents a regression from the 2.8 behavior for schema fields. 2.8 appears to be able to derive this behavior from the CRDs. Steve should aim to have similar behavior.

[MbolotSuse]

Issue Summary

Currently, the schema definitions retrieves the fields available for a resource from the openapi/v2 endpoint, as seen here. When creating a CRD, users can specify the openAPISchema for the type in spec.versions[0].schema.openAPIV3Schema. Since this specification is using the openapi v3 specification, users can specify fields/types here that aren't compatible with the openapi v2. In these cases, the openapi v2 specification will contain only a "type: string" for the type, rather than the required complex field information.

[tomleb]

This is currently blocked on https://github.com/rancher/rancher/pull/45483 because steve is using k8s 1.30 / wrangler v3 but that's not yet in rancher/rancher.