Update hcp-dc-tls-hosted.adoc

[Sourav21jain]

https://issues.redhat.com/browse/OSDOCS-15916

Version(s):

4.18 +

Issue:

https://issues.redhat.com/browse/OSDOCS-15916

Link to docs preview:

QE review:

• QE has approved this change.

[openshift-ci]

Hi @Sourav21jain. 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.

[Sourav21jain]

/label merge-review-needed

[Sourav21jain]

/label merge-review-needed

[openshift-ci]

@Sourav21jain: Can not set label merge-review-needed: Must be member in one of these teams: [team-red-hat]

Details

In response to this:

/label merge-review-needed

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.

[Sourav21jain]

/label merge-review-needed

[stevsmit]

Content changes LGTM, but it'll need QE ack before merging.

[Sourav21jain]

Hello @stevsmit Can we get this progressed? If you can check with the QE? @heliubj18 Can you help on this?

[bergerhoffer]

The branch/enterprise-4.21 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.20. And any PR going into main must also target the latest version branch (enterprise-4.21).

If the update in your PR does NOT apply to version 4.21 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[bergerhoffer]

The branch/enterprise-4.22 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.21. And any PR going into main must also target the latest version branch (enterprise-4.22).

If the update in your PR does NOT apply to version 4.22 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.