We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--disable-cloud-provider
cloud-provider=
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
cloudProviderName
The DisableExternalCloudProvider flag should be deprecated in the upcoming v1beta2 version.
An equivalent config would then be:
serverConfig: disableCloudProvider: true cloudProviderName: external
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
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:
The text was updated successfully, but these errors were encountered: