[CP 1388] Create DeviceClass from operator code on OpenShift when DRA is enabled#530
Open
ci-penbot-01 wants to merge 1 commit intoROCm:mainfrom
Conversation
…d (#1388) * Create DeviceClass from operator code on OpenShift when DRA is enabled On OpenShift, operator-sdk cannot deploy DeviceClass resources via the OLM bundle. This adds handleDeviceClass to the reconciler which creates the gpu.amd.com DeviceClass using an unstructured client when running on OpenShift with DRA driver enabled. The DeviceClass is cluster-scoped and shared, so it is created once (AlreadyExists is handled gracefully) and never deleted on DeviceConfig finalization. * Use deviceClassName constant instead of hardcoded string Address review feedback: extract "gpu.amd.com" into a const and use it throughout handleDeviceClass. (cherry picked from commit d8845e69298bab8e21f2c0955a4b6579bc79ea76)
Contributor
Author
AI-Assisted Cherry-PickSource PR: #1388 The cherry-pick operation encountered merge conflicts which were resolved automatically using AI assistance. Files with conflicts (resolved by AI):
Original conflict in bundle/manifests/amd-gpu-operator.clusterserviceversion.yaml<<<<<<< HEAD
createdAt: "2026-04-06T08:31:30Z"
=======
createdAt: "2026-04-22T01:09:34Z"
>>>>>>> d8845e69... Create DeviceClass from operator code on OpenShift when DRA is enabled (#1388)Cherry-pick triggered by: ACP-Automation |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
cp of pensando/gpu-operator#1388
Source PR Description (pensando/gpu-operator#1388):
On OpenShift, operator-sdk cannot deploy DeviceClass resources via the OLM bundle. This adds handleDeviceClass to the reconciler which creates the gpu.amd.com DeviceClass using an unstructured client when running on OpenShift with DRA driver enabled. The DeviceClass is cluster-scoped and shared, so it is created once (AlreadyExists is handled gracefully) and never deleted on DeviceConfig finalization.
Cherrypick triggered by: ACP-Automation