Skip to content

SOLR StatefulSet gets a broken securityContext by default #466

Open
@tux-o-matic

Description

@tux-o-matic

Upon deploying a SolrCloud CR for the first time with the Operator (version 0.6.0), ZK is fine but the SOLR StatefulSet fails to start Pods because of:

create Pod demo-solrcloud-0 in StatefulSet demo-solrcloud failed error: pods "demo-solrcloud-0" is forbidden: unable to validate against any security context constraint: [provider restricted: .spec.securityContext.fsGroup: Invalid value: []int64{8983}: 8983 is not an allowed group provider restrictedfsgroup: .spec.securityContext.fsGroup: Invalid value: []int64{8983}: 8983 is not an allowed group]

If in the SolrCloud CR I specify an empty context, everything start fine:

spec:
  customSolrKubeOptions:
    podOptions:
      podSecurityContext: {}

I don't know if this is expected, a bug or some edge case for OpenShift but there was no documentation for it.

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