GPU Operator v26.7.0 release notes omit the ComputeDomain CRD ownership conflict with the DRA driver chart

What the docs say

The v26.7.0 Known Issues section in gpu-operator/release-notes.rst lists a single
issue (DRA passthrough allocation), and the GPUCluster Limitations in
gpu-operator/dra-intro-install.rst cover migration and GKE overrides. Neither
covers ownership of the ComputeDomain CRD when the DRA driver is installed from
its own Helm chart alongside the GPU Operator chart.

What appears to be true

Both charts ship the ComputeDomain CRD, so ownership of it conflicts when both
are installed. A plain helm install does not surface this, because Helm does not
record release ownership for CRDs installed from crds/ — but a GitOps installer
that does track ownership, such as Argo CD, fails on it. This is a common
deployment shape on GB200, where multi-node NVLink is exactly what ComputeDomains
are for, so the affected population overlaps heavily with the users of the
feature.

Suggested fix

A Known Issue entry under v26.7.0 with the workaround: skip CRDs in the GPU
Operator chart and apply the ClusterPolicy and NVIDIADriver CRDs separately.
Worth stating explicitly whether the same conflict applies when the Operator is
installed via OLM and the DRA driver via Helm.

Start with the v26.7.0 Known Issues section in gpu-operator/release-notes.rst and the GPUCluster Limitations in gpu-operator/dra-intro-install.rst. Document the ComputeDomain CRD ownership conflict when the DRA driver is installed by Helm, include the suggested CRD workaround, and state whether the same issue applies to OLM-installed Operator deployments. Verify that the Known Issues entry and installation guidance are consistent.