You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ba6cc85
Browse filesBrowse the repository at this point in the historyBrowse files
Complete the DCGM Exporter ServiceAccount support on the GPUCluster path
Review feedback: the first commit wired the field on the ClusterPolicy path only,
leaving the DRA path able to render the reference without honouring the contract
behind it.
- pass the field through deployments/gpu-operator/templates/gpucluster.yaml, so a
Helm GPUCluster install can set it;
- add a preSync hook to configurableState and use it for the exporter, so
create: false reports NotReady when the ServiceAccount is missing rather than
leaving the DaemonSet pending on an object the manifests deliberately omit;
- refuse to take over a ServiceAccount that already exists under a configured name
and is not owned by the CR. createOrUpdateObjs() would otherwise adopt it on the
DRA path and hand it to garbage collection with the GPUCluster. The default name
stays tolerant so an upgrade that lost the owner reference keeps converging;
- reclaim the operator-owned default ServiceAccount once a different name takes
over, on both paths. Renaming between two custom names is not tracked, so only
the default is reclaimed;
- cover the GPUCluster path: the rendered ServiceAccount, DaemonSet and RBAC
subjects for a custom name, the omitted ServiceAccount for create: false, and
each preSync branch.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UiFVTVAyEMmn68Xvo9LSTf
Signed-off-by: 백지명 <wlaud9805@gmail.com>
0 commit comments