Open rriverak opened 5 months ago
All previous images are still available: https://github.com/jaegertracing/spark-dependencies/pkgs/container/spark-dependencies%2Fspark-dependencies/versions
Running latest
in production is not commended.
Sadly, the ci.yaml does not include any tests against Cassandra, only Elasticsearch. It also doesn't log anything about containers being executed - would be nice to include docker logs
as an after-step.
All previous images are still available: https://github.com/jaegertracing/spark-dependencies/pkgs/container/spark-dependencies%2Fspark-dependencies/versions
Running
latest
in production is not commended.
The lack of other Tags makes it difficult to use anything other than latest
in Production. (which is simply default)
We have now referenced the SHA of the old Image, which is also not recommended for Production.
A versioning according to SemVer would be helpful to allow Image Pinning by the Jaeger Operator.
What happened?
Since the last update (20 days ago) of the Docker image which overwrote the 'latest' tag, the spark-job of the jaeger-operator stopped Working.
see operator issue here: https://github.com/jaegertracing/jaeger-operator/issues/2508
Steps to reproduce
Use the latest version of jaeger-operator (1.49.0) and the Spark-jobs will fail.
Expected behavior
At least the old Docker-Image should be available. Overwriting the latest tag prevents any Workaround.
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
Kubernetes
Deployment configs
No response