-
Notifications
You must be signed in to change notification settings - Fork 51
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 what cloud prepare does on each platform #801
Comments
These are the steps that need to be followed.
|
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
The dependency on |
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
It seems like we need a section of the website generally describing cloud prepare, what it does for all platforms. |
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
subctl cloud prepare
is typically strongly tied to OpenShift, and documented as only supported on OpenShift (e.g. at least on some platforms it relies onMachineSet
support). For non-OpenShift users, it would be useful to document whatcloud prepare
does on each platform, so that users can replicate its work manually.The text was updated successfully, but these errors were encountered: