mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
55 lines
3.6 KiB
Plaintext
55 lines
3.6 KiB
Plaintext
:_mod-docs-content-type: ASSEMBLY
|
|
[id="virt-automatic-bootsource-updates"]
|
|
= Managing automatic boot source updates
|
|
include::_attributes/common-attributes.adoc[]
|
|
:context: virt-automatic-bootsource-updates
|
|
|
|
toc::[]
|
|
|
|
You can manage automatic updates for the following boot sources:
|
|
|
|
* xref:../../virt/storage/virt-automatic-bootsource-updates.adoc#managing-rh-boot-source-updates_virt-automatic-bootsource-updates[All Red Hat boot sources]
|
|
* xref:../../virt/storage/virt-automatic-bootsource-updates.adoc#managing-custom-boot-source-updates_virt-automatic-bootsource-updates[All custom boot sources]
|
|
* xref:../../virt/storage/virt-automatic-bootsource-updates.adoc#virt-disable-auto-updates-single-boot-source_virt-automatic-bootsource-updates[Individual Red Hat or custom boot sources]
|
|
|
|
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 Red Hat boot sources.
|
|
|
|
[id="managing-rh-boot-source-updates_virt-automatic-bootsource-updates"]
|
|
== Managing Red Hat boot source updates
|
|
|
|
You can opt out of automatic updates for all system-defined boot sources by setting the `enableCommonBootImageImport` field value to `false`. If you set the value to `false`, all `DataImportCron` objects are deleted. This does not, however, remove previously imported boot source objects that store operating system images, though administrators can delete them manually.
|
|
|
|
When the `enableCommonBootImageImport` field value is set to `false`, `DataSource` objects are reset so that they no longer point to the original boot source. An administrator can manually provide a boot source by creating a new persistent volume claim (PVC) or volume snapshot for the `DataSource` object, and then populating it with an operating system image.
|
|
|
|
include::modules/virt-managing-auto-update-all-system-boot-sources.adoc[leveloffset=+2]
|
|
|
|
[id="managing-custom-boot-source-updates_virt-automatic-bootsource-updates"]
|
|
== Managing custom boot source updates
|
|
|
|
_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).
|
|
|
|
ifndef::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
|
|
[IMPORTANT]
|
|
====
|
|
You must configure a storage class. Otherwise, the cluster cannot receive automated updates for custom boot sources. See xref:../../storage/dynamic-provisioning.adoc#defining-storage-classes_dynamic-provisioning[Defining a storage class] for details.
|
|
====
|
|
endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
|
|
ifdef::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
|
|
[IMPORTANT]
|
|
====
|
|
You must configure a storage profile. Otherwise, the cluster cannot receive automated updates for custom boot sources. See xref:../../virt/storage/virt-configuring-storage-profile.adoc#virt-configuring-storage-profile[Configure storage profiles] for details.
|
|
====
|
|
endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
|
|
|
|
include::modules/virt-configuring-default-and-virt-default-storage-class.adoc[leveloffset=+2]
|
|
|
|
include::modules/virt-configuring-storage-class-bootsource-update.adoc[leveloffset=+2]
|
|
|
|
include::modules/virt-autoupdate-custom-bootsource.adoc[leveloffset=+2]
|
|
|
|
include::modules/virt-enabling-volume-snapshot-boot-source.adoc[leveloffset=+2]
|
|
|
|
include::modules/virt-disable-auto-updates-single-boot-source.adoc[leveloffset=+1]
|
|
|
|
include::modules/virt-verify-status-bootsource-update.adoc[leveloffset=+1]
|