Closed anmazzotti closed 6 months ago
The current implementation of DisableExternalCloudProvider is a bit confusing (sorry for that).
DisableExternalCloudProvider
As discussed in this comment, it would be more explicit to have two dedicated fields in the server config:
disableCloudProvider
--disable-cloud-provider
cloudProviderName
The DisableExternalCloudProvider flag should be deprecated in the upcoming v1beta2 version.
An equivalent config would then be:
serverConfig: disableCloudProvider: true cloudProviderName: external
The current implementation of
DisableExternalCloudProvider
is a bit confusing (sorry for that).As discussed in this comment, it would be more explicit to have two dedicated fields in the server config:
disableCloudProvider
to add the--disable-cloud-provider
feature flag on k3s.cloudProviderName
to set an explicit cloud provider name.The
DisableExternalCloudProvider
flag should be deprecated in the upcoming v1beta2 version.An equivalent config would then be: