-
Notifications
You must be signed in to change notification settings - Fork 101
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
https://issues.redhat.com/browse/ACM-14417 Ver. Strategy doc #7222
base: 2.12_stage
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: oafischer The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@oafischer can we also mention the strategy when creating/importing a cluster, if it is a ROSA-HCP cluster, should check if the 1.6.4 Cluster creation 1.6.5 Cluster import |
@elgnay please help take a review, thx! |
Co-authored-by: Jian Zhu <[email protected]>
Co-authored-by: Jian Zhu <[email protected]>
@zhujian7 We can add the pre-flight info but I'm not sure where a good spot for it would be. In our creating and import doc, we do not have anything related to ROSA. HCP content has also moved to OCP docs entirely in 2.12, so we don't have any HCP docs left in ACM docs where this could fit in either. When reading pre-flight info, it sounds like it applies to more than just ROSA HCP. Is that the case? |
If so, I think it's OK without the pre-flight info. @elgnay WDYT? |
@oafischer @zhujian7 I still think we need to add one more item to the prerequisites of cluster creation and cluster importing:
Since the default strategy 'UseAutoDetectedCABundle' may not work always, it necessary for the user to review the hub API server certificate verification strategy before they start creating or importing managed clusters. |
LGTM |
Train 19