Skip to content

Loosen schema value restrictions for OKD compatibility #1716

@shastaxc

Description

@shastaxc

What would you like to be added?

OpenShift Kubernetes Distribution (OKD) automatically sets user and group for workloads. If setting these manually conflicts with the IDs OKD wants to use, it will throw an error. To help ensure compatibility, I generally just set these values to null and let OKD handle it. However, the Helm schema files do not allow null values. I would like the schemas to be updated to allow null values for the following settings:

podTemplate:
  spec:
    securityContext:
      fsGroup: null
      runAsUser: null

console:
  podSecurityContext:
    runAsUser: null
    fsGroup: null
    fsGroupChangePolicy: null

Why is this needed?

Compatibility with OpenShift Kubernetes Distribution.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions