Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SOLR StatefulSet gets a broken securityContext by default #466

Open
tux-o-matic opened this issue Aug 18, 2022 · 1 comment · May be fixed by #706
Open

SOLR StatefulSet gets a broken securityContext by default #466

tux-o-matic opened this issue Aug 18, 2022 · 1 comment · May be fixed by #706

Comments

@tux-o-matic
Copy link

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.

@HoustonPutman
Copy link
Contributor

Sorry for the late reply. You can see this issue #264 on how someone was able to get the Solr Operator to work with OpenShift. However, we should probably have documentation for common work-arounds for various cloud platforms.

computate added a commit to computate/solr-operator that referenced this issue May 25, 2024
Adding an openshift boolean field to the operator to remove the default
Solr fsGroup in Kubernetes.

Fixes apache#466
@computate computate linked a pull request May 25, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants