Most RKE1 Cluster YAML keys are not validated before cluster creation

[rosskirkpat]

Setup

• Rancher version: v2.6.5-rc1
• Browser type & version: Firefox 98.0.2 on MacOS 12.2.1

Describe the bug

Most RKE1 cluster yaml keys are not validated prior to cluster creation. Any keys that are are camel cased or begin with an uppercase letter are not flagged as invalid and the values for those keys will be lost once the cluster is created.

To Reproduce
Create an RKE1 cluster by editing via YAML and using uppercase keys

Result
Any keys that are uppercase are replaced with their default values and lose the configured value.

Expected Result
The UI should validate all cluster yaml keys and block cluster creation if any configured keys are invalid, same as it does for name and rancher_kubernetes_engine_config.

Additional context
It currently appears to only validate the name and rancher_kubernetes_engine_config keys

Here are the three cluster yamls from each stage shown in the screenshots

Screenshots

[rosskirkpat]

This issue was discovered while investigating a docs issue with secret_encryption_config in RKE1 clusters.

Following the docs here, I specified the following in kube_api:

Before:

    kube_api:
      always_pull_images: false
      pod_security_policy: false
      secrets_encryption_config:
        enabled: true
        custom_config:
          api_version: apiserver.config.k8s.io/v1
          kind: EncryptionConfiguration
          Resources:
          - Providers:
            - AESCBC:
                Keys:
                  - Name: key1
                    Secret: b6E0EuBMGOV86UVC76SzUqRAxECZOdK7+tWSzaIP4dk=
              Resources:
                - secrets
            - identity: {}
        service_node_port_range: 30000-32767

This configuration passed validation but ended up as

    kube-api:
      always_pull_images: false
      pod_security_policy: false
      secrets_encryption_config:
        custom_config:
          api_version: apiserver.config.k8s.io/v1
          kind: EncryptionConfiguration
        enabled: true
      service_node_port_range: 30000-32767

After:

[catherineluse]

It should be a higher priority to fix the docs issue (the incorrectly capitalized keys https://rancher.com/docs/rke/latest/en/config-options/secrets-encryption/#example-using-custom-encryption-configuration-with-user-provided-32-byte-random-key) than it is to add this validation here. Normally we only validate the forms, whereas in YAML, we expect the user to be following docs. So if there's a problem with the docs, that should be fixed first.

I have opened a docs ticket here: https://github.com/rancher/docs/issues/4346

[gaktive]

Closing since docs were updated and validation not possible in code.