1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/virt-installing-virt-operator.adoc
2025-11-18 16:29:25 +01:00

62 lines
2.8 KiB
Plaintext

// Module included in the following assemblies:
//
// * virt/install/installing-virt.adoc
:_mod-docs-content-type: PROCEDURE
[id="virt-installing-virt-operator_{context}"]
= Installing the {VirtProductName} Operator by using the web console
[role="_abstract"]
You can deploy the {VirtProductName} Operator by using the {product-title} web console.
.Prerequisites
* Install {product-title} {product-version} on your cluster.
* Log in to the {product-title} web console as a user with `cluster-admin` permissions.
// required for ROSA/OSD
ifdef::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
* Create a machine pool based on a bare metal compute node instance type. For more information, see "Creating a machine pool" in the Additional resources of this section.
endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
.Procedure
. From the *Administrator* perspective, click *Ecosystem* -> *Software Catalog*.
. In the *Filter by keyword* field, type *Virtualization*.
. Select the *{CNVOperatorDisplayName}* tile with the *Red Hat* source label.
. Read the information about the Operator and click *Install*.
. On the *Install Operator* page:
.. Select *stable* from the list of available *Update Channel* options. This ensures that you install the version of {VirtProductName} that is compatible with your {product-title} version.
.. For *Installed Namespace*, ensure that the *Operator recommended namespace* option is selected. This installs the Operator in the mandatory `{CNVNamespace}` namespace, which is automatically created if it does not exist.
+
[WARNING]
====
Attempting to install the {VirtProductName} Operator in a namespace other than `{CNVNamespace}` causes the installation to fail.
====
.. For *Approval Strategy*, it is highly recommended that you select *Automatic*, which is the default value, so that {VirtProductName} automatically updates when a new version is available in the *stable* update channel.
+
Selecting the *Manual* approval strategy is not recommended, as it poses a high risk to cluster support and functionality. Only select *Manual* if you fully understand these risks and cannot use *Automatic*.
+
[WARNING]
====
Because {VirtProductName} is only supported when used with the corresponding {product-title} version, missing {VirtProductName} updates can cause your cluster to become unsupported.
====
. Click *Install* to make the Operator available to the `{CNVNamespace}` namespace.
. When the Operator installs successfully, click *Create HyperConverged*.
. Optional: Configure *Infra* and *Workloads* node placement options for {VirtProductName} components.
. Click *Create* to launch {VirtProductName}.
.Verification
* Navigate to the *Workloads* -> *Pods* page and monitor the {VirtProductName} pods until they are all *Running*. After all the pods display the *Running* state, you can use {VirtProductName}.