Schema.json drop 'required' for security contexts

[user170200]

Background

Platforms with security contexts (SCCs), such as Openshift (or OKD) require specific values for fsGroup or runAsUser.
The final values are namespace-dependent - a security feature of these platforms.
It would be rather messy to retrieve the dynamically required values from the platform and generate a custom value.yaml for each stage+namespace.

However, platforms using SCCs can set these values automatically, given they are non-present or set to NULL.

The Problem

The values.schema.json sets these properties as 'required'.
If they are set to null, each helm command must use the --skip-schema-validation or fail.

A possible solution

Dropping these fields to be 'required' - They can still be set, they still show up normally, but are nullable and support platforms with SCCs.

[Copilot]

Pull request overview

Adjusts the Helm chart JSON schema to better support platforms (e.g., OpenShift/OKD with SCCs) where fsGroup/runAsUser may need to be omitted so the platform can default them per-namespace.

Changes:

• Removes required constraints for podSecurityContext.fsGroup.
• Removes required constraints for securityContext.capabilities.drop.
• Removes required constraints for securityContext fields (capabilities, runAsNonRoot, runAsUser).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[user170200]

Verified the behavior described by CoPilot and applied the changes:

Let the fsGroup and runAsUser be of type: ["integer", "null"] instead.

Updated the commit to stay clean