Skip to content

pgadmin4-helm initContainers with hardcoded securityContext does not work on OpenShift #9646

@eidottermihi

Description

@eidottermihi

Describe the bug

Using the pgadmin4-helm Helm Chart does not work on OpenShift because the initContainers uses a hard coded securityContext:

To Reproduce

helm upgrade --install pgadmin4 oci://docker.io/dpage/pgadmin4-helm

Expected behavior

IMO the initContainers should get the same securityContext as the main container ( https://github.com/pgadmin-org/pgadmin4/blob/master/pkg/helm/templates/deployment.yaml#L101 )

Error message

pods "pgadmin4-7b84bfbf6-" is forbidden: unable to validate against any security context constraint: [provider "anyuid": Forbidden: not usable by user or serviceaccount, provider restricted-v2: .initContainers[0].runAsUser: Invalid value: 1001: must be in the ranges: [1003310000, 1003319999], provider restricted-v2: .initContainers[0].seLinuxOptions.level: Invalid value: "": must be s0:c58,c2, provider restricted-v2: .initContainers[1].runAsUser: Invalid value: 1001: 

Metadata

Metadata

Assignees

Type

No type

Projects

Status

🆕 New

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions