ROCm / ROCm/gpu-operator

[Issue]: Update DevceConfig driver version to supported driver version for each release

Open
#406 1 comment 0 reactions 1 assignee View on GitHub

@yansun1996 is already working on this.

Since Jan 8, 2026.

documentation enhancement
Dominant language
Go
Stars
105
Forks
57
Avg merge
1d 2h
Merged PRs (30d)
12

Description

Problem Description

When specifying a bare minimum DeviceConfig on OpenShift that enables the driver but does not specify the version, the operator will set .spec.driver.version = 6.2.2. This is no longer a supported version for building on OCP v4.20.z clusters (k8s v1.33) causing the driver will fail to build due to the

The recommendation is to update the default driver version to match what is the currently supported version for each release unless you want to make the driver.version mandatory

$ oc version
Server Version: 4.20.8
Kubernetes Version: v1.33.6
Operating System

OCP 4.20.8

CPU

N/A

GPU

N/A

ROCm Version

6.2.2

ROCm Component

No response

Steps to Reproduce
  1. Deploy a DeviceConfig that does not specify .spec.driver.version
apiVersion: amd.com/v1alpha1
kind: DeviceConfig
metadata:
  namespace: openshift-amd-gpu
  name: test-deviceconfig
spec:
  devicePlugin:
    devicePluginImage: docker.io/rocm/k8s-device-plugin:latest
    nodeLabellerImage: docker.io/rocm/k8s-device-plugin:labeller-latest
  driver:
    enable: true
    #version: 6.2.2  #<--- Not required for successful DeviceConfig deployment
  selector:
    feature.node.kubernetes.io/amd-gpu: 'true'
  1. Once deployed, the module build will pass DRIVERS_VERSION=6.2.2 as the KMM build argument.

test-deviceconfig-build-wnj8d-build-docker-build.log

(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support

No response

Additional Information

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.