-
Notifications
You must be signed in to change notification settings - Fork 111
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
Document migration steps to CCM #42
Comments
To get started, a rough outline:
There will be certain differences between different cloud providers, as compatibility between integrated and external cannot always be guaranteed. |
I think this warrants a page in the official Kubernetes docs, @onitake are you willing to put something together? |
Yes, I think I can do that.
|
And also, where should the documentation live?
|
I think we should stick to documenting one, AWS is probably the best example because of # of users that manage it themselves. The steps should mostly be the same across all providers as well
I think we can assume control plane nodes are separate nodes
I think for the first pass, we should ignore storage providers and add CSI migration documentation iteratively.
No, I think just showing how to validate your CCM is working is fine
I think something like |
I launched a PR, please submit corrections and input on how to migrate on AWS. I'm slightly biased towards private cloud CCM migrations, so please public cloud users: Give input on your cloud environment specifics. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
/lifecycle frozen |
/cc @jiahuif |
/assign @jiahuif |
/cc @jpbetz |
We should document how a user would manually migrate their clusters from using in-tree cloud providers to out-of-tree cloud provider. The documented steps can be manual or via a tool like kubeadm.
The text was updated successfully, but these errors were encountered: