You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, the provider section is not output in the mke4.yaml output with mkectl init. When no providers are specified, MKE will only enable the sveltos provider because MKE4 depends on it. Once providers are specified, if sveltos is not one of them, it will be added.
The config to add providers to the MKE4 looks like
Note
Due to an issue with k0rdent that we are waiting on the next release to get a fix for, all providers are installed when the cluster is created. Once the cluster is up and running, the additional providers are disabled so they are not running.
The text was updated successfully, but these errors were encountered:
Document how MKE4 is configuring k0rdent CAPI providers.
https://github.com/MirantisContainers/mke/pull/475
https://github.com/MirantisContainers/mke-operator/pull/217
By default, the provider section is not output in the mke4.yaml output with
mkectl init
. When no providers are specified, MKE will only enable the sveltos provider because MKE4 depends on it. Once providers are specified, if sveltos is not one of them, it will be added.The config to add providers to the MKE4 looks like
Any valid k0rdent providers will work.
Note
Due to an issue with k0rdent that we are waiting on the next release to get a fix for, all providers are installed when the cluster is created. Once the cluster is up and running, the additional providers are disabled so they are not running.
The text was updated successfully, but these errors were encountered: