Skip to content

docs: document standalone DRA CRD conflicts #504

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
efegokdemir wants to merge 1 commit into from
+4 −0
Closed

docs: document standalone DRA CRD conflicts #504

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions gpu-operator/release-notes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -189,6 +189,10 @@ Known Issues

To avoid conflicting allocations, submit the workloads serially and wait for device preparation to complete, or dedicate separate nodes to container and VFIO workloads.

* If you install the DRA Driver for NVIDIA GPUs from its own Helm chart alongside GPU Operator, both charts install the ComputeDomain custom resource definitions (CRDs).
GitOps tools that track CRD ownership can report a conflict between the two releases.
Do not install the standalone DRA chart with the ``GPUCluster`` workflow. If you use the standalone chart instead, install GPU Operator with ``--skip-crds`` and apply the ``ClusterPolicy`` and ``NVIDIADriver`` CRDs separately before creating those resources.

Post-Release Documentation Updates
----------------------------------

Expand Down