[🐛 Bug]: chromeNode.service.enabled regression

[aidanthewiz]

What happened?

While attempting to upgrade to selenium-grid-0.38.0/4.27.0-20241127, I received this error:

Error: template: selenium-grid/templates/chrome-node-service.yaml:8:24: executing "selenium-grid/templates/chrome-node-service.yaml" at <.Release.Namespace>: nil pointer evaluating interface {}.Namespace

#2475 appears to be the cause, with the below minimum replication (broken.yaml):

chromeNode:
  service:
    enabled: true

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

helm upgrade --install selenium-grid docker-selenium/selenium-grid --namespace selenium -f broken.yaml

Relevant log output

Error: template: selenium-grid/templates/chrome-node-service.yaml:8:24: executing "selenium-grid/templates/chrome-node-service.yaml" at <.Release.Namespace>: nil pointer evaluating interface {}.Namespace

Operating System

Kubernetes 1.30.5 on Docker Desktop 4.36.0 (175267) on macOS 15.2 Beta (24C5089c)

Docker Selenium version (image tag)

4.27.0-20241127

Selenium Grid chart version (chart version)

0.38.0

[github-actions]

@aidanthewiz, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[VietND96]

Thanks for your report. This and something else are ongoing to fix and will be out in chart 0.38.1.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.