Merge pull request #63037 from sabrinajess/CNV30685

CNV-30685: RHEL subscription info

Author: mburke5678

modules/virt-about-auto-bootsource-updates.adoc

@@ -9,8 +9,10 @@
 
 Boot sources can make virtual machine (VM) creation more accessible and efficient for users. If automatic boot source updates are enabled, the Containerized Data Importer (CDI) imports, polls, and updates the images so that they are ready to be cloned for new VMs. By default, CDI automatically updates the _system-defined_ boot sources that {VirtProductName} provides.
 
-You can opt out of automatic updates for all system-defined boot sources by disabling the `enableCommonBootImageImport` feature gate. If you disable this feature gate, all `DataImportCron` objects are deleted. This does not remove previously imported `PersistentVolumeClaim` (PVC) objects that store operating system images, though administrators can delete them manually. 
+You can opt out of automatic updates for all system-defined boot sources by disabling the `enableCommonBootImageImport` feature gate. If you disable this feature gate, all `DataImportCron` objects are deleted. This does not remove previously imported `PersistentVolumeClaim` (PVC) objects that store operating system images, though administrators can delete them manually.
 
 When the `enableCommonBootImageImport` feature gate is disabled, `DataSource` objects are reset so that they no longer point to the original PVCs. An administrator can manually provide a boot source by creating a new PVC for the `DataSource` object and populating the PVC with an operating system image.
 
-_Custom_ boot sources that are not provided by {VirtProductName} are not controlled by the feature gate. You must manage them individually by editing the `HyperConverged` custom resource (CR). You can also use this method to manage individual system-defined boot sources.
+_Custom_ boot sources that are not provided by {VirtProductName} are not controlled by the feature gate. You must manage them individually by editing the `HyperConverged` custom resource (CR). You can also use this method to manage individual system-defined boot sources.
+
+Cluster administrators can enable automatic subscription for {op-system-base-full} virtual machines in the {VirtProductName} xref:../../virt/getting_started/virt-web-console-overview.adoc#overview-settings-cluster_virt-web-console-overview[web console].

virt/getting_started/virt-web-console-overview.adoc

@@ -251,6 +251,11 @@ To store Red Hat templates in multiple projects, xref:../../virt/getting_started
 
 Preview features are disabled by default and must not be enabled in production environments.
 
+|*Automatic subscription of new RHEL VirtualMachines* section
+|Expand this section to enable automatic subscription for {op-system-base-full} VirtualMachines.
+
+Cluster administrator permissions are required to enable this feature.
+
 |*LoadBalancer* section
 |Expand this section to enable the creation of load balancer services for SSH access to virtual machines.
 

virt/virtual_machines/virt-create-vms.adoc

@@ -28,6 +28,8 @@ You can expedite VM creation by using templates that have an available boot sour
 
 Templates without a boot source are labeled *Boot source required*. You can use these templates if you complete the steps for xref:../../virt/vm_templates/virt-creating-vm-template.adoc#virt-adding-a-boot-source-web_virt-creating-vm-template[adding a boot source to the virtual machine].
 
+Cluster administrators can enable automatic subscription for {op-system-base-full} virtual machines in the {VirtProductName} xref:../../virt/getting_started/virt-web-console-overview.adoc#overview-settings-cluster_virt-web-console-overview[web console].
+
 [NOTE]
 ====
 You can customize the template or VM parameters before you start the VM.