[Bug]: Missing support for extraSecretMounts

[finki77]

What happened?

In file charts/jaeger/templates/jaeger/jaeger-deploy.yaml there's no support for mounting extra secrets. These are required for example when establishing a TLS connection to a storage backend using a self-signed certificate.

Steps to reproduce

n/a

Expected behavior

In chart version 1, there was allInOne.extraSecretMounts in values.yaml. This should also work in Chart version 2.

Relevant log output

Screenshot

No response

Additional context

No response

Jaeger backend version

No response

SDK

No response

Pipeline

No response

Stogage backend

No response

Operating system

No response

Deployment model

No response

Deployment configs

[igor-nikiforov]

I can confirm that it's currently not possible to configure an Elasticsearch / Opensearch connection to clusters with self-signed certificates due to this issue.

[fr0stnk]

Same issue here, using elasticsearch with self-signed CA. In v1 allInOne.extraSecretMounts was the way to go, now theres literally no way to mount the cert into the pod.
Ended up with insecure: true as only option which is not great for prod. The ca_file field in userconfig is pointless without being able to actually mount the file somewhere.

[jbouse]

Reporting that I've also been bit with this... It seems that upgrading from chart v4.3.4 to v4.4.0 the jaeger.envFrom and jaeger.extraSecretMounts functionality was removed from the Deployment templates. Both of these mean I can't upgrade beyond 4.3.4 as I inject the ElasticSearch credentials via a secretRef along with mounting our internal CA certificate managed via a Cert Manager Trust Bundle secret. Without these the pod goes into an endless crashbackloop.