Skip to content

[enterprise-4.22] CCSINTL-3575: Short desc CQA fixes #114237

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
abrennan89 merged 1 commit into from
Jun 26, 2026
+18 −13
Merged

[enterprise-4.22] CCSINTL-3575: Short desc CQA fixes #114237

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion modules/virt-about-upgrading-virt.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion modules/virt-configuring-root-ca-for-providers.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
10 changes: 6 additions & 4 deletions modules/virt-creating-primary-udn-web-intro.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
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.
2 changes: 1 addition & 1 deletion modules/virt-customizing-storage-profile-snapshot-class-cli.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down
4 changes: 2 additions & 2 deletions modules/virt-customizing-storage-profile-snapshot-class-web.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand All @@ -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*.
. Click *Save*.
9 changes: 5 additions & 4 deletions modules/virt-supported-cluster-version.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand All @@ -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]
Expand Down