Skip to content

[gpu-op] Dotted ConfigMap names generate invalid driver volumes in ClusterPolicy and NVIDIADriver #3204

Open

Description

@rahulait

Describe the bug

Driver configuration referencing a ConfigMap whose name contains dots produces an invalid driver DaemonSet in both the ClusterPolicy and NVIDIADriver paths.

ConfigMap names follow DNS subdomain naming rules, which allow dots. However, the operator copies the ConfigMap name directly into Pod volume names and corresponding volume mounts. Volume names follow DNS label rules and cannot contain dots.

Affected settings, verified independently in both paths:

  • repoConfig
  • certConfig
  • kernelModuleConfig

To reproduce

Create a ConfigMap in the GPU Operator namespace:

apiVersion: v1
kind: ConfigMap
metadata:
  name: driver.config
data:
  custom.list: |
    # Custom repository configuration

Reference it using either configuration below.

For an otherwise valid ClusterPolicy:

spec:
  driver:
    repoConfig:
      configMapName: driver.config

For an otherwise valid NVIDIADriver:

spec:
  repoConfig:
    name: driver.config

The resulting driver DaemonSet includes:

volumes:
  - name: driver.config
    configMap:
      name: driver.config

The generated volume name violates Kubernetes naming rules, making the DaemonSet Pod template invalid.

Expected behavior

Generate a valid, deterministic volume name and use it consistently in volume mounts. Preserve the original ConfigMap name in configMap.name.

Code locations

Both files contain createConfigMapVolumeMounts and createConfigMapVolume helpers that use the ConfigMap name directly:

  • controllers/object_controls.go — ClusterPolicy path
  • internal/state/driver.go — NVIDIADriver path

Activity

  1. added
    good-first-issueIssues that are friendly to new contributors
    and removed
    needs-triageissue or PR has not been assigned a priority-px label
    on Nov 9, 2026
  2. shenyv1 commented on Nov 10, 2026

    @shenyv1

    I'd like to work on this issue. Could you please assign it to me?

  3. rahulait commented on Nov 10, 2026

    @rahulait
    ContributorAuthor

    @shenyv1 assigned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

good-first-issueIssues that are friendly to new contributors

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions