joshsouza commented on issue #475:
URL: https://github.com/apache/solr-operator/issues/475#issuecomment-1255636822
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"
-
"https://repo1.maven.org/maven2/software/amazon/awssdk/sts/2.15.54/sts-2.15.54.jar";,
- "-o"
- "/output/sts-2.15.54.jar"
volumeMounts:
- name: "sts"
mountPath: "/output"
volumes:
- name: "sts"
source:
emptyDir: {}
defaultContainerMount:
name: "sts"
mountPath: "/opt/solr/dist/sts-2.15.54.jar"
subPath: "sts-2.15.54.jar"
```
Clearly this isn't a long-term solution, but this puts the `sts` module in
the `/opt/solr/dist` directory on the pods, thus adding it to the classpath
that the Operator puts in place, and have confirmed that after doing so S3
backups are working properly.
Should we open an issue with the main Apache Solr project to address this?
--
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: issues-unsubscr...@solr.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
