CNV - 64510: TP to GA boost on ARO

[Vaishali-gif-rh]

Version(s):
4.20

Issue:
https://issues.redhat.com/browse/CNV-64510

Link to docs preview:
https://100987--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/install/preparing-cluster-for-virt.html#compatible-platforms_preparing-cluster-for-virt

QE review:

• QE has approved this change.

Additional information:

[ocpdocs-previewbot]

🤖 Mon Oct 27 13:29:33 - Prow CI generated the docs preview:

https://100987--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/install/preparing-cluster-for-virt.html
https://100987--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/virt/install/preparing-cluster-for-virt.html
https://100987--ocpdocs-pr.netlify.app/openshift-rosa/latest/virt/install/preparing-cluster-for-virt.html

[geetikakay]

lgtm

[jherrman]

Very straightforward change, nothing to complain about here :-)

One thing I noticed, though, is that the heading of the section has an un-rendered {VirtProductName} attribute, which I don't think should happen even in the preview.

[Vaishali-gif-rh]

@jherrman - Thanks for pointing that out! Just to be sure I fix the right spot, are you referring to the {VirtProductName} in the Azure Red Hat OpenShift (preview) heading (around line 78), or another heading?

[jherrman]

@Vaishali-gif-rh , no, I meant the "Preparing your cluster for {VirtProductName}" heading in https://100987--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/install/preparing-cluster-for-virt.html#compatible-platforms_preparing-cluster-for-virt

In the source file, it is on line 3.

[openshift-ci]

@Vaishali-gif-rh: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/validate-portal	4a7d778	link	true	/test validate-portal
ci/prow/validate-asciidoc	4a7d778	link	true	/test validate-asciidoc

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.