🐛 Bug Report: Config validation does not allow for custom k8s authProvider

[Jenson3210]

📜 Description

After changing our default authProvider from serviceAccount to a custom one as explained in the docs, our production version fails to start.

With
authStrategy.addAuthStrategy('pinniped', pinnipedStrategy);
it will be required to have in the app-config.production.yaml

kubernetes:
  serviceLocatorMethod:
    type: 'singleTenant'
  clusterLocatorMethods:
    - type: 'config'
      clusters:
        - url: ...
          name: ...
          authProvider: pinniped

NOTE: it does not need to be pinniped but this string might be any other possibility.

👍 Expected behavior

Startup succeeds and uses the provided authProvider.

👎 Actual Behavior with Screenshots

Loading config from MergedConfigSource{FileConfigSource{path="/app/app-config.yaml"}, FileConfigSource{path="/app/app-config.production.yaml"}, EnvConfigSource{count=0}}
...
throw new errors.ForwardedError(
^
Error: Plugin 'app' startup failed; caused by Error: Invalid app bundle schema. If this error is unexpected you need to run `yarn build` in the app. If that doesn't help you should make sure your config schema is correct and rebuild the app bundle again. Caused by the following schema error, Error: Config validation failed, Config must be equal to one of the allowed values { allowedValues=aks,aws,azure,google,googleServiceAccount,oidc,serviceAccount } at /kubernetes/clusterLocatorMethods/0/clusters/0/authProvider; Config must be equal to one of the allowed values { allowedValues=aks,aws,azure,google,googleServiceAccount,oidc,serviceAccount } at /kubernetes/clusterLocatorMethods/0/clusters/1/authProvider; Config must be equal to one of the allowed values { allowedValues=aks,aws,azure,google,googleServiceAccount,oidc,serviceAccount } at /kubernetes/clusterLocatorMethods/0/clusters/2/authProvider; Config must be equal to constant { allowedValue=catalog } at 

Config must be equal to one of the allowed values { allowedValues=aks,aws,azure,google,googleServiceAccount,oidc,serviceAccount }

Do I miss documentation on how to extend the schema OR is this simply not possible?

👟 Reproduction steps

Just follow the docs for custom authProvider.

Configure the yaml to use this provider.

📃 Provide the context for the Bug.

• I think this config value should just be a string type instead of an array of possibilities?
• seems like clusterLocatorMethods is also not correct in the schema

🖥️ Your Environment

No response

👀 Have you spent some time to check if this bug has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

Are you willing to submit PR?

Yes I am willing to submit a PR!