Skip to content

[🐛 Bug]:extraVolumeMounts and extraVolumes cause template rendering failure in Helm chart under videomanager components #2827

Closed
@ndambi2024

Description

@ndambi2024

What happened?

When using videoManager.extraVolumeMounts or videoManager.extraVolumes in the official Selenium Grid Helm chart, the Helm template fails with an error like:
json: cannot unmarshal object into Go struct field Container.spec.template.spec.containers.volumeMounts of type []v1.VolumeMount
This is caused by the template rendering the extraVolumeMounts and extraVolumes values incorrectly — treating them as objects rather than arrays.

Command used to start Selenium Grid with Docker (or Kubernetes)

Use this minimal values.yaml
videoManager:
  enabled: true
  extraVolumeMounts:
    - name: srv
      mountPath: /srv
  extraVolumes:
    - name: srv
      persistentVolumeClaim:
        claimName: my-pvc

Relevant log output

":\"2025-05-05T17:47:36Z\",\"lastTransitionTime\":\"2025-05-05T17:47:36Z\",\"reason\":\"MinimumReplicasAvailable\",\"message\":\"Deployment has minimum availability.\"}]}}": json: cannot unmarshal object into Go struct field Container.spec.template.spec.containers.volumeMounts of type []v1.VolumeMount

Operating System

EKS

Docker Selenium version (image tag)

4.32.0-20250505

Selenium Grid chart version (chart version)

0.43.0

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions