Enable passing securityContext to initContainers in the Helm chart

[calendir]

User description

Description

A simple change adding the missing securityContext fields to the initContainers so that they can be set for those along with the regular containers.

Motivation and Context

When security policies are enforced in a cluster that the default configuration does not comply with the pre-puller-* pods will not be allowed to start, even though securityContext is set.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have read the contributing document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

---

PR Type

Bug fix, Enhancement

---

Description

• Added securityContext support for initContainers in Helm chart.

• Ensured compatibility with enforced cluster security policies.

• Updated pre-puller-* pods to include securityContext.

---

Changes walkthrough 📝

	Relevant files
Enhancement	_helpers.tpl Add `securityContext` to `initContainers` and containers  charts/selenium-grid/templates/_helpers.tpl Added securityContext field for node containers. Added securityContext field for recorder containers. Ensured securityContext is configurable for initContainers. +6/-0

---

Need help?

Type /help how to ... in the comments thread for any question about Qodo Merge usage.

Check out the documentation for more information.

[CLAassistant]

All committers have signed the CLA.

[qodo-code-review]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Command Validation The command ["bash", "-c", "'true'"] has unnecessary single quotes around 'true' which may cause the command to fail. Should be ["bash", "-c", "true"] instead. command: ["bash", "-c", "'true'"]

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Fix command string literal format Remove the single quotes around 'true' in the command field. In Kubernetes/Helm, the command should be a plain string without quotes, as the single quotes will be interpreted literally. charts/selenium-grid/templates/_helpers.tpl [318] -command: ["bash", "-c", "'true'"] +command: ["bash", "-c", "true"] Apply this suggestion Suggestion importance[1-10]: 8 Why: The single quotes around 'true' in the command field would be interpreted literally by Kubernetes, potentially causing command execution issues. This is a significant fix that affects container initialization functionality.	8

[VietND96]

Thank you, @calendir. I merged to include it in next chart deployment.