Skip to content

Commit 7046b1f

Browse files
authored
Merge pull request #174 from hershpa/kmm
kmmo: Update RHOCP version links in readme
2 parents 14ed6af + 89bab45 commit 7046b1f

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

kmmo/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,14 +12,14 @@ Intel data center GPU driver container images are released from [Intel Data Cent
1212
- **On-premises build mode** - Users can optionally build and deploy their own driver container images on-premises through the KMM operator.
1313

1414
# Prerequisites
15-
- Provisioned RHOCP 4.12 cluster. Follow steps [here](/README.md#provisioning-rhocp-cluster).
15+
- Provisioned RHOCP cluster. Follow steps [here](/README.md#provisioning-rhocp-cluster).
1616
- Setup node feature discovery. Follow steps [here](/nfd/README.md).
1717
- Setup machine configuration. Follow steps [here](/machine_configuration/README.md).
1818

1919
# Install KMM operator
2020
Follow the installation guide below to install the KMM operator via CLI or web console.
21-
- [Install from CLI](https://docs.openshift.com/container-platform/4.12/hardware_enablement/kmm-kernel-module-management.html#kmm-install-using-cli_kernel-module-management-operator)
22-
- [Install from web console](https://docs.openshift.com/container-platform/4.12/hardware_enablement/kmm-kernel-module-management.html#kmm-install-using-web-console_kernel-module-management-operator)
21+
- [Install from CLI](https://docs.openshift.com/container-platform/4.13/hardware_enablement/kmm-kernel-module-management.html#kmm-install-using-cli_kernel-module-management-operator)
22+
- [Install from web console](https://docs.openshift.com/container-platform/4.13/hardware_enablement/kmm-kernel-module-management.html#kmm-install-using-web-console_kernel-module-management-operator)
2323

2424
# Canary deployment with KMM
2525
Canary deployment is enabled by default to deploy the driver container image only on specific node(s) to ensure the initial deployment succeeds prior to rollout to all the eligible nodes in the cluster. This safety mechanism can reduce risk and prevent a deployment from adversely affecting the entire cluster.

0 commit comments

Comments
 (0)