-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OSDOCS#15587: CQA updates #96824
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
OSDOCS#15587: CQA updates #96824
Conversation
|
@skopacz1: This pull request references OSDOCS-15587 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
🤖 Tue Aug 05 16:35:46 - Prow CI generated the docs preview: |
| ---- | ||
|
|
||
| . To create a region tag for each region vSphere data center where you want to deploy your cluster, enter the following command in your terminal: | ||
| . For each region vSphere data center where you want to deploy your cluster, create a region tag by running the following command: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| . For each region vSphere data center where you want to deploy your cluster, create a region tag by running the following command: | |
| . For each region where you want to deploy your cluster, create a region tag by running the following command: |
| ---- | ||
|
|
||
| . To create a zone tag for each vSphere cluster where you want to deploy your cluster, enter the following command: | ||
| . For each vSphere cluster where you want to deploy your cluster, create a zone tag by running the following command: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| . For each vSphere cluster where you want to deploy your cluster, create a zone tag by running the following command: | |
| . For each zone where you want to deploy your cluster, create a zone tag by running the following command: |
|
/lgtm |
c9105ce to
8b36151
Compare
|
@skopacz1: No Jira issue is referenced in the title of this pull request. 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 openshift-eng/jira-lifecycle-plugin repository. |
8b36151 to
a16631d
Compare
|
/lgtm |
| <1> Leave the `claim` field blank to allow the automatic creation of an `image-registry-storage` persistent volume claim (PVC). The PVC is generated based on the default storage class. However, be aware that the default storage class might provide ReadWriteOnce (RWO) volumes, such as a RADOS Block Device (RBD), which can cause issues when you replicate to more than one replica. | ||
|
|
||
| . Check the `clusteroperator` status: | ||
| . Check the `clusteroperator` status by running the following command: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is a big gap, let me try and delete that
|
Hi, @skopacz1 . Getting near the end of my day so me waiting for CPs to pass might not suit you . Feel free to merge the PR. I added one minor comment inline. |
|
LGTM |
a16631d to
4226a31
Compare
|
New changes are detected. LGTM label has been removed. |
|
@skopacz1: 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. |
|
/cherrypick enterprise-4.16 |
|
@skopacz1: #96824 failed to apply on top of branch "enterprise-4.16": 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-sigs/prow repository. |
|
/cherrypick enterprise-4.17 |
|
@skopacz1: new pull request created: #97176 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-sigs/prow repository. |
|
@skopacz1: new pull request created: #97177 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-sigs/prow repository. |
|
@skopacz1: new pull request created: #97178 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-sigs/prow repository. |
|
@skopacz1: new pull request created: #97179 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-sigs/prow repository. |

🚨NOTE TO MERGE REVIEWER: I have merge rights, feel free to leave merging to me after your review, but it's okay if you merge it yourself.
OSDOCS-15587
Version(s): 4.17+
This PR makes style level edits to vSphere IPI install content as a result of doing a CQA.
QE review:
Previews: