-
Notifications
You must be signed in to change notification settings - Fork 347
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]: Spark no longer works with new charts that use elasticsearch 8+ #574
Comments
Need to update the registry in the chart based on this comment. #532 (comment) Make the correct registry part of the chart |
@dpericaxon @yurishkuro Why is sparkdependencies hosted in github and the rest are hosted on docker? https://github.com/orgs/jaegertracing/packages That is a bit confusing especially since there is on on docker that is claimed to be outdated via jaegertracing/spark-dependencies#137 (comment) |
I don't know how/why that decision was made. I agree it would've been better to use the same Docker and Quay hosting we use for other images. |
I updated the readme for spark-dependencies. I think this Helm chart should be pointing to a different location too: helm-charts/charts/jaeger/values.yaml Line 781 in f4213e2
|
Yeah that link to the values is what I meant by #574 (comment) I can make a PR. I think just setting the registry and repo to default to the ghcr.io will be fine. I did this locally since we use the global.imageRegistry. Then it will work out if the box for others. |
I fixed it by adding the registry and repository to my configuration as follows. spark:
enabled: true
image:
registry: ghcr.io
repository: jaegertracing/spark-dependencies/spark-dependencies |
What happened?
As a user of the "system architecture" tab in Jaeger I would like to use Spark to generate the diagrams.
But spark no longer works with new charts that use elasticsearch 8+
Spark job throws logs stating that it requires elasticsearch 7 and hadoop.
Steps to reproduce
Expected behavior
spark job completes as it used to
Relevant log output
Screenshot
No response
Additional context
No response
Jaeger backend version
3.0.7
SDK
No response
Pipeline
No response
Stogage backend
Elasticsearch 8+
Operating system
Linux
Deployment model
Kubernetes
Deployment configs
The text was updated successfully, but these errors were encountered: