[OSDOCS-17008] CQA 2.1 for vSphere IPI installer-provisioned

[maxwelldb]

Version(s): 4.20+

Issue: OSDOCS-17008

Link to docs preview: 4.20+

QE review:

• QE has approved this change.

Additional information: CQA pre-migration pass for the base installer-provisioned assembly.

[openshift-ci-robot]

@maxwelldb: This pull request references OSDOCS-17008 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 sub-task to target the "5.0.0" version, but no target version was set.

Details

In response to this:

What

CQA 2.0/2.1 pre-migration pass for installing/installing_vsphere/ipi/installing-vsphere-installer-provisioned.adoc and its included modules, part of OSDOCS-17008 (vSphere IPI, under epic OSDOCS-16987 / INSTALL-6).

Changes

• Added missing [role="_abstract"] short description to the assembly's intro paragraph.
• Extracted the "Creating registry storage" heading and its intro sentence — previously sitting directly in the assembly body between module includes — into a new modules/installing-vsphere-installer-provisioned-registry-reference.adoc REFERENCE module, clearing the AssemblyContents hit.
• Moved the "Configuring the registry for vSphere" and "About remote health monitoring" cross references out of prose sentences into proper module-level .Additional resources blocks, clearing ConceptLink/RelatedLinks hits.

Deliberately left as is (matches epic-wide precedent)

• The Prerequisites and Next steps sections' embedded xrefs are unchanged. This copy-pasted structural pattern (a heading with prose/xrefs directly in the assembly body, rather than a proper Additional resources block) is confirmed present and unresolved on the AWS, GCP, and Nutanix installer-provisioned assemblies too — see CQA-pass-criteria.md's "Before touching a widespread pattern" guidance. Fixing it here would be a bigger, more content-altering change than the rest of this CQA pass and would make vSphere diverge from its siblings.
• modules/cluster-entitlements.adoc's link:http://quay.io[Quay.io] ConceptLink hit is left as is — a prior CQA commit (c79a79c276793855e186f70184bbd83ae0cb93d3, OSDOCS-17013) already fixed this shared module's ShortDescription but intentionally left this link, so this PR matches that precedent rather than diverging.

Verification

• vale --config=.vale-test.ini (AsciiDocDITA package) shows only the deferred hits above and one known NoXrefInModules false positive on the new, properly-formed Additional resources blocks.
• Rendered with asciidoctor -d book to confirm heading structure and TOC nesting are unchanged.

No technical/content meaning changed; this is a structural CQA pass only.

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.

[ocpdocs-previewbot]

🤖 Mon Jul 13 18:31:10 - Prow CI generated the docs preview:

https://115236--ocpdocs-pr.netlify.app/openshift-enterprise/latest/installing/installing_vsphere/ipi/installing-vsphere-installer-provisioned.html

[openshift-ci]

@maxwelldb: all tests passed!

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.

[openshift-ci-robot]

@maxwelldb: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

What

CQA 2.0/2.1 pre-migration pass for installing/installing_vsphere/ipi/installing-vsphere-installer-provisioned.adoc and its included modules, part of OSDOCS-17008 (vSphere IPI, under epic OSDOCS-16987 / INSTALL-6).

Changes

• Added missing [role="_abstract"] short description to the assembly's intro paragraph.
• Extracted the "Creating registry storage" heading and its intro sentence — previously sitting directly in the assembly body between module includes — into a new modules/installing-vsphere-installer-provisioned-registry-reference.adoc REFERENCE module, clearing the AssemblyContents hit.
• Moved the "Configuring the registry for vSphere" and "About remote health monitoring" cross references out of prose sentences into proper module-level .Additional resources blocks, clearing ConceptLink/RelatedLinks hits.

Deliberately left as is (matches epic-wide precedent)

• The Prerequisites and Next steps sections' embedded xrefs are unchanged. This copy-pasted structural pattern (a heading with prose/xrefs directly in the assembly body, rather than a proper Additional resources block) is confirmed present and unresolved on the AWS, GCP, and Nutanix installer-provisioned assemblies too — see CQA-pass-criteria.md's "Before touching a widespread pattern" guidance. Fixing it here would be a bigger, more content-altering change than the rest of this CQA pass and would make vSphere diverge from its siblings.
• modules/cluster-entitlements.adoc's link:http://quay.io[Quay.io] ConceptLink hit is left as is — a prior CQA commit (c79a79c276793855e186f70184bbd83ae0cb93d3, OSDOCS-17013) already fixed this shared module's ShortDescription but intentionally left this link, so this PR matches that precedent rather than diverging.

Verification

• vale --config=.vale-test.ini (AsciiDocDITA package) shows only the deferred hits above and one known NoXrefInModules false positive on the new, properly-formed Additional resources blocks.
• Rendered with asciidoctor -d book to confirm heading structure and TOC nesting are unchanged.

No technical/content meaning changed; this is a structural CQA pass only.

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.