Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: [jaeger] can't affect storage.elasticseach.host value #632

Open
s-dwinter opened this issue Feb 23, 2025 · 0 comments
Open

[Bug]: [jaeger] can't affect storage.elasticseach.host value #632

s-dwinter opened this issue Feb 23, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@s-dwinter
Copy link

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.

{{- if .Values.provisionDataStore.elasticsearch }}
{{- $host = printf "%s-elasticsearch" .Release.Name }}
{{- end }}

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 than 3.3.2 version.

provisionDataStore:
  cassandra: false
  elasticsearch: true

storage:
  type: elasticsearch

  elasticsearch:
    host: custom-host

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

@s-dwinter s-dwinter added the bug Something isn't working label Feb 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant