-
Notifications
You must be signed in to change notification settings - Fork 38.7k
New issue
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
Collect tips for external cloud provider migration #120411
Comments
/sig cloud-provider docs |
only if uses the
|
thanks for starting this @dims ! |
/triage accepted |
I would like to know if there is any docs regarding the GCE migration, existing clusters and new ones, thanks we will need this for capg |
@cpanato i'm not finding an GCE specific docs for migration, but we do have these 2 general docs about migrating (depending on whether you are using HA or not):
we will capture the general tips for migration and troubleshooting in the KEP but for GCE specific guidance this is something that should be requested in the cloud-provider-gcp repository. i have a feeling there will be more requests like this for specific cloud provider documentation and i think we will need to focus our efforts on having the individual providers create documentation as it will not scale well to centralize this knowledge for all providers. |
is this only for gcp? |
@elmiko for all providers |
/close |
@dims: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
DisableCloudProviders
istrue
(by default or explicitly)DisableKubeletCloudCredentialProviders
istrue
(by default or explicitly)--image-credential-provider-config
and--image-credential-provider-bin-dir
( see Set external credential provider to true by default in kube-up.sh #120392 ).node-ipam-controller
in the value of--controllers
parametercloud
version of thecontroller-manager
The text was updated successfully, but these errors were encountered: