Skip to content

Commit cc7cb17

Browse files
a-mccarthytariq1890
andcommitted
add openshift clusterpolicy create webconsole docs
Signed-off-by: Abigail McCarthy <[email protected]> Co-authored-by: Tariq <[email protected]>
1 parent 4b8f7a0 commit cc7cb17

File tree

6 files changed

+48
-3
lines changed

6 files changed

+48
-3
lines changed
126 KB
Loading
137 KB
Loading
142 KB
Loading
114 KB
Loading
150 KB
Loading

openshift/openshift-virtualization.rst

Lines changed: 48 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -286,8 +286,8 @@ private container registry).
286286
.. _install-cluster-policy-vGPU:
287287

288288

289-
Creating a ClusterPolicy for the GPU Operator
290-
=============================================
289+
Creating a ClusterPolicy for the GPU Operator using the OpenShift Container Platform CLI
290+
=========================================================================================
291291

292292
As a cluster administrator, you can create a ClusterPolicy using the OpenShift Container Platform CLI.
293293
Create the cluster policy using the CLI:
@@ -330,6 +330,52 @@ Without additional configuration, the GPU Operator creates a default set of devi
330330
To learn more about how the vGPU Device Manager and configure which types of vGPU devices get created in your cluster, refer to :ref:`vGPU Device Configuration<vgpu-device-configuration>`.
331331

332332

333+
Creating a ClusterPolicy for the GPU Operator using the OpenShift Container Platform Web Console
334+
================================================================================================
335+
336+
As a cluster administrator, you can create a ClusterPolicy using the OpenShift Container Platform web console.
337+
338+
#. Navigate to **Operators** > **Installed Operators** and find your installed NVIDIA GPU Operator.
339+
340+
#. Under *Provided APIs*, click **ClusterPolicy**.
341+
342+
343+
.. image:: graphics/navigate_to_cluster_policy.png
344+
345+
346+
#. Click **Create ClusterPolicy**.
347+
348+
.. image:: graphics/create_cluster_policy.png
349+
350+
#. Expand the **NVIDIA GPU/vGPU Driver config** section.
351+
352+
#. Expand the **Sandbox Workloads config** section and select the checkbox to enable sandbox workloads.
353+
354+
In general, when sandbox workloads are enabled, ``ClusterPolicy`` controls whether the GPU Operator can provision GPU worker nodes for virtual machine workloads, in addition to container workloads. This flag is disabled by default, meaning all nodes get provisioned with the same software which enables container workloads, and the ``nvidia.com/gpu.workload.config`` node label is not used.
355+
356+
The term ``sandboxing`` refers to running software in a separate isolated environment, typically for added security (i.e. a virtual machine). We use the term ``sandbox workloads`` to signify workloads that run in a virtual machine, irrespective of the virtualization technology used.
357+
* Click **Create** to create the ClusterPolicy.
358+
359+
.. image:: graphics/cluster_policy_enable_sandbox_workloads.png
360+
361+
#. If you are planning to use NVIDIA vGPU, expand the **NVIDIA vGPU Manager config** section and fill in your desired configuration settings, including:
362+
363+
* Select the **enabled** checkbox to enable the NVIDIA vGPU Manager.
364+
* Add your **imagePullSecrets**.
365+
* Under *driverManager*, fill in **repository** with the path to your private repository.
366+
* Under *env*, fill in **image** with ``vgpu-manager`` and the **version** with your driver version.
367+
368+
If you are only using GPU passthrough, you dont need to fill this section out.
369+
370+
.. image:: graphics/cluster_policy_configure_vgpu.png
371+
372+
#. Click **Create** to create the ClusterPolicy.
373+
374+
The vGPU Device Manager, deployed by the GPU Operator, automatically creates vGPU devices which can be assigned to KubeVirt VMs.
375+
Without additional configuration, the GPU Operator creates a default set of devices on all GPUs.
376+
To learn more about the vGPU Device Manager and how to configure which types of vGPU devices get created in your cluster, refer to :ref:`vGPU Device Configuration<vgpu-device-configuration>`.
377+
378+
333379
*******************************************************
334380
Add GPU Resources to the HyperConverged Custom Resource
335381
*******************************************************
@@ -404,7 +450,6 @@ The following example permits the A10 GPU device and A10-24Q vGPU device.
404450

405451
Refer to the `KubeVirt user guide <https://kubevirt.io/user-guide/virtual_machines/host-devices/#listing-permitted-devices>`_ for more information on the configuration options.
406452

407-
408453
About Mediated Devices
409454
======================
410455

0 commit comments

Comments
 (0)