OSDOCS-17464: address QE feedback for Helm UI location (4.21)

[jseseCCS]

Version(s): 4.21

Issue: OSDOCS-17464

Link to docs preview:

QE review:
[x] QE has approved this change.

[openshift-ci-robot]

@jseseCCS: This pull request references OSDOCS-17464 which is a valid jira issue.

Details

In response to this:

…ease notes

Version(s):

Issue:

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

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.

[openshift-ci-robot]

@jseseCCS: This pull request references OSDOCS-17464 which is a valid jira issue.

Details

In response to this:

Version(s): 4.21

Issue: OSDOCS-17464

Link to docs preview:

QE review:
[x] QE has approved this change.

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.

[openshift-ci-robot]

@jseseCCS: This pull request references OSDOCS-17464 which is a valid jira issue.

Details

In response to this:

Version(s): 4.21

Issue: OSDOCS-17464

Link to docs preview:

QE review:
[x] QE has approved this change.

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.

[openshift-ci]

Hi @jseseCCS. 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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[jseseCCS]

@yapei @Leo6Leo making your changes, Ya Dan! please review this one and please also see my comments in the original PR. thank you!