janhoy commented on issue #671: URL: https://github.com/apache/solr-operator/issues/671#issuecomment-6476181082
The reporter resolved this with a dedicated ServiceAccount and SecurityContextConstraints, which is the normal way to run Solr on OpenShift today — the SCC posted in this thread is a useful reference for others hitting the same error. The two operator-side gaps this thread uncovered are now tracked separately: - #466 — the hardcoded `fsGroup: 8983` that an empty `customSolrKubeOptions.podOptions.podSecurityContext` cannot clear, which is what OpenShift's `restricted-v2` SCC rejects. It has a fresh report against OpenShift 4.20. - #873 — making the operator's generated pods PSA "restricted"-compatible by default, which is the broader proposal from the discussion here, for all clusters rather than behind an OpenShift switch. Closing this one so the work happens in those two. Thanks @aaronsuns for digging out both the patch and the SCC. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
