-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OCPBUGS#45054: Maintain linear nomenclature for nodes in the "Installing Cluster on any platform" documentation #85475
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
base: main
Are you sure you want to change the base?
Conversation
Hi @Atharva-Shinde. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
/ok-to-test |
🤖 Tue Dec 03 05:52:17 - Prow CI generated the docs preview: |
… of the platform agnostic cluster installation documentation
43a7a5e
to
f1c3e78
Compare
/label peer-review-needed |
Co-authored-by: Alex Dellapenta <[email protected]>
@Atharva-Shinde: all tests passed! Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
Hey @adellape any updates on this PR? |
The This is because your PR targets the If the update in your PR does NOT apply to version 4.19 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main. |
Version(s): 4.17, 4.16, 4.15, 4.14, 4.13, 4.12
Issue: Jira Ticket
Link to docs preview:
QE review:
Additional information:
Changed the node names in the HAProxy configuration from
master<>
tocontrol-plane<>