You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been customizing the elasticsearch hostname using the jaeger helm chart by specifying the storage.elasticsearch.host variable. However, since version 3.3.2, the value I provided is being overwritten with a different one. I suspect this is due to changes introduced in the following section in v3.3.2.
What happened?
I have been customizing the elasticsearch hostname using the jaeger helm chart by specifying the
storage.elasticsearch.host
variable. However, since version 3.3.2, the value I provided is being overwritten with a different one. I suspect this is due to changes introduced in the following section in v3.3.2.helm-charts/charts/jaeger/templates/_helpers.tpl
Lines 272 to 274 in 9c9abf4
I believe there are users, like myself, who customize the hostname, so I think
$host
should not be overwritten.Steps to reproduce
You use this
values.yaml
and use jaeger helm chart newer than3.3.2
version.Expected behavior
The value specified for
storage.elasticsearch.host
to be reflected in the manifests.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
The text was updated successfully, but these errors were encountered: