bcbrockway commented on issue #489:
URL: https://github.com/apache/solr-operator/issues/489#issuecomment-2368300581
To the maintainers: Is there a particular reason you specify your own fields
in podOptions.podSecurityContext instead of just accepting a [k8s
podSecurityContext API
type](ht
bentastic27 commented on issue #489:
URL: https://github.com/apache/solr-operator/issues/489#issuecomment-2096660400
I'm running into this issue on EKS.
@janhoy / @HoustonPutman Are these extra capabilties/privs ever actually
needed? If not, we can likely hardcode in the changes made
janhoy commented on issue #489:
URL: https://github.com/apache/solr-operator/issues/489#issuecomment-2092905796
> Hi all! a new version was recently released (April 12, 2024, Apache Solr
Operator™ v0.8.1 available, there is no solution to our problem) is there any
news on our problem?
AyzekTime commented on issue #489:
URL: https://github.com/apache/solr-operator/issues/489#issuecomment-2092685981
Hi all! a new version was recently released (April 12, 2024, Apache Solr
Operator™ v0.8.1 available, there is no solution to our problem) is there any
news on our problem?
--
HoustonPutman commented on issue #489:
URL: https://github.com/apache/solr-operator/issues/489#issuecomment-2021124458
No news from me. I'm not running openshift, so I don't really know what
needs to be done. If someone wants to start a PR, then I'm very happy to help
usher it through.
aaronsuns commented on issue #489:
URL: https://github.com/apache/solr-operator/issues/489#issuecomment-1875059878
Any news on this one?
--
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 specif
