From fd022fe44782e7468ca39810ca672e0a62ea0de5 Mon Sep 17 00:00:00 2001 From: Ashleigh Brennan Date: Fri, 26 Jun 2026 12:06:54 -0500 Subject: [PATCH] CCSINTL-3575: Short desc CQA fixes --- modules/virt-about-upgrading-virt.adoc | 4 +++- modules/virt-configuring-root-ca-for-providers.adoc | 2 +- modules/virt-creating-primary-udn-web-intro.adoc | 10 ++++++---- ...customizing-storage-profile-snapshot-class-cli.adoc | 2 +- ...customizing-storage-profile-snapshot-class-web.adoc | 4 ++-- modules/virt-supported-cluster-version.adoc | 9 +++++---- 6 files changed, 18 insertions(+), 13 deletions(-) diff --git a/modules/virt-about-upgrading-virt.adoc b/modules/virt-about-upgrading-virt.adoc index f394a94ce3e0..0128d46826fc 100644 --- a/modules/virt-about-upgrading-virt.adoc +++ b/modules/virt-about-upgrading-virt.adoc @@ -8,7 +8,9 @@ = About updating {VirtProductName} [role="_abstract"] -When you install {VirtProductName}, you select an update channel and an approval strategy. The update channel determines the version of {VirtProductName} that you use. The approval strategy determines whether updates occur automatically or require manual approval. Both settings affect supportability. +When you install {VirtProductName}, you select an update channel and an approval strategy. Both settings affect supportability. + +The update channel determines the version of {VirtProductName} that you use. The approval strategy determines whether updates occur automatically or require manual approval. [id="recommended-settings_{context}"] == Recommended settings diff --git a/modules/virt-configuring-root-ca-for-providers.adoc b/modules/virt-configuring-root-ca-for-providers.adoc index b3043cb5ce44..29a891e17f36 100644 --- a/modules/virt-configuring-root-ca-for-providers.adoc +++ b/modules/virt-configuring-root-ca-for-providers.adoc @@ -7,7 +7,7 @@ = Configuring the root certificate authority for providers [role="_abstract"] -You must configure an {product-title} provider for each cluster that you are including in the migration, and each provider requires a certificate authority (CA) for the cluster. It is important to configure the root CA for the entire cluster to avoid CA expiration, which causes the provider to fail. +You must configure an {product-title} provider for each cluster that you are including in a migration, and each provider requires a certificate authority (CA) for the cluster. It is important to configure the root CA for the entire cluster to avoid CA expiration, which causes the provider to fail. .Procedure diff --git a/modules/virt-creating-primary-udn-web-intro.adoc b/modules/virt-creating-primary-udn-web-intro.adoc index fbf677f42775..51b7ed2dce7f 100644 --- a/modules/virt-creating-primary-udn-web-intro.adoc +++ b/modules/virt-creating-primary-udn-web-intro.adoc @@ -2,11 +2,13 @@ // // * virt/vm_networking/virt-connecting-vm-to-primary-udn.adoc -:_mod-docs-content-type: REFERENCE -[id="virt-creating-primary-udn-web-intro_{context}"] +:_mod-docs-content-type: CONCEPT +[id="virt-creating-primary-udn-web-intro_{context}"] = Create a primary user-defined network by using the web console [role="_abstract"] -You can use the {product-title} web console to create a primary namespace-scoped `UserDefinedNetwork` or a cluster-scoped `ClusterUserDefinedNetwork` custom resource definition (CRD). The UDN serves as the default primary network for pods and VMs that you create in namespaces associated with the network. +You can use the {product-title} web console to create a primary namespace-scoped `UserDefinedNetwork` (UDN) or a cluster-scoped `ClusterUserDefinedNetwork` custom resource definition (CRD). -After you define the custom primary overlay network, you can create namespaces that are associated with the cluster-scoped UDN. \ No newline at end of file +The UDN serves as the default primary network for pods and VMs that you create in namespaces associated with the network. + +After you define the custom primary overlay network, you can create namespaces that are associated with the cluster-scoped UDN. diff --git a/modules/virt-customizing-storage-profile-snapshot-class-cli.adoc b/modules/virt-customizing-storage-profile-snapshot-class-cli.adoc index f01d9e9bf528..2da7b016dc89 100644 --- a/modules/virt-customizing-storage-profile-snapshot-class-cli.adoc +++ b/modules/virt-customizing-storage-profile-snapshot-class-cli.adoc @@ -7,7 +7,7 @@ = Specifying a volume snapshot class by using the CLI [role="_abstract"] -If you are creating a snapshot of a VM, a warning is displayed if the storage class of the disk has more than one volume snapshot class associated with it. In this case, you must specify one volume snapshot class; otherwise, any disk that has more than one volume snapshot class is excluded from the snapshots list. +If you are creating a snapshot of a VM, you must specify only one volume snapshot class. Any disk that has more than one volume snapshot class is excluded from the snapshots list. A warning is displayed if the storage class of the disk has more than one volume snapshot class associated with it. You can select which volume snapshot class to use by either: diff --git a/modules/virt-customizing-storage-profile-snapshot-class-web.adoc b/modules/virt-customizing-storage-profile-snapshot-class-web.adoc index 7f3708f8c5ec..2635d610b4f1 100644 --- a/modules/virt-customizing-storage-profile-snapshot-class-web.adoc +++ b/modules/virt-customizing-storage-profile-snapshot-class-web.adoc @@ -7,7 +7,7 @@ = Specifying a volume snapshot class by using the web console [role="_abstract"] -If you are creating a snapshot of a VM, a warning is displayed if the storage class of the disk has more than one volume snapshot class associated with it. In this case, you must specify one volume snapshot class. Otherwise, any disk that has more than one volume snapshot class is excluded from the snapshots list. +If you are creating a snapshot of a VM, you must specify only one volume snapshot class. Any disk that has more than one volume snapshot class is excluded from the snapshots list. A warning is displayed if the storage class of the disk has more than one volume snapshot class associated with it. You can specify the default volume snapshot class in the {product-title} web console. @@ -19,4 +19,4 @@ You can specify the default volume snapshot class in the {product-title} web con . Click the *Annotations* pencil icon. . Enter the following *Key*: `snapshot.storage.kubernetes.io/is-default-class`. . Enter the following *Value*: `true`. -. Click *Save*. \ No newline at end of file +. Click *Save*. diff --git a/modules/virt-supported-cluster-version.adoc b/modules/virt-supported-cluster-version.adoc index 381a9e60b75e..e7f178d60990 100644 --- a/modules/virt-supported-cluster-version.adoc +++ b/modules/virt-supported-cluster-version.adoc @@ -8,6 +8,11 @@ = Supported cluster versions for {VirtProductName} [role="_abstract"] +ifndef::openshift-dedicated[] +{VirtProductName} {VirtVersion} is supported for use on {product-title} {product-version} clusters. To use the latest z-stream release of {VirtProductName}, you must first upgrade to the latest version of {product-title}. +The latest stable release of {VirtProductName} {VirtVersion} is {HCOVersion}. +endif::openshift-dedicated[] + ifdef::openshift-dedicated[] {VirtProductName} on {gcp-short} is supported on {product-title} using either {gcp-short} Hyperdisk or {gcp-short} NetApp Volumes (GCNV) for persistent storage. @@ -21,10 +26,6 @@ Refer to the following table for the minimum version you need to install based o |NetApp Trident CSI Operator |N/A |26.02.0 or later |=== endif::openshift-dedicated[] -ifndef::openshift-dedicated[] -{VirtProductName} {VirtVersion} is supported for use on {product-title} {product-version} clusters. To use the latest z-stream release of {VirtProductName}, you must first upgrade to the latest version of {product-title}. -The latest stable release of {VirtProductName} {VirtVersion} is {HCOVersion}. -endif::openshift-dedicated[] ifdef::openshift-rosa,openshift-rosa-hcp[] [NOTE]