Josh Souza

I 100% support adding a cluster-level PDB here, as that's definitely a first step towards success. My concern is that the PDB will ensure we don't take a pod down...

Ideas our team has been tossing around in discussions: `startupProbe` may also reduce risk (though still allows for some edge cases). If a newly starting pod had a startup probe...

(Read up more carefully on the docs, we can't use the sidecar idea, because it would indicate the whole pod isn't ready, and drop it from the service)

Just had a thought on this after perusing the docs further to see if there's anything I could find to support our end goals within current constraints: https://kubernetes.io/docs/tasks/run-application/configure-pdb/#specifying-a-poddisruptionbudget I can...

It also occurred to me that if each SolrCloud had a PDB with a `maxUnavailable` of `0` _at all times_, the Solr Operator could monitor the cluster for node rotation...

Thanks for all the thoughtful discussion. It hadn't even occurred to me to do a per-pod pdb, but that makes a ton of sense given the context, and I would...

As far as I can tell, the `sts` module isn't included in the `s3-repository` contrib module: https://repo1.maven.org/maven2/org/apache/solr/solr-s3-repository/8.11.2/solr-s3-repository-8.11.2.pom This lacks: ``` software.amazon.awssdk sts 2.15.20 ``` So this may be on the...

I have confirmed this by adding the following to the helm values (which propagate to the SolrCloud CRD): ``` podOptions: initContainers: - name: "add-sts" image: "alpine/curl" command: - "curl" -...

Thanks! I'll see if we can try out the UTO for now!