Steven

Seeing how the old elasticsearch chart is deprecated and the suggestion is to use ECK now but has license issues to consider. I suggest doing what we did when we...

helm charts were just updated to 1.53 https://github.com/jaegertracing/helm-charts/commit/94950b7c837ccdde786ffb3308132cc759a374ca. This implies that I can use elasticsearch 8+ . Any work on ensuring this is true and updateing the chart to point...

Awesome thanks! I'll try to get to it this week. Did you get to test esIndexCleaner it other items? I guess they should be fine since those images are in...

I have had issues similar to this when running dependency packages... There were two cases that happened often (0.9.9.8); 1. I had referenced an xml file that had bad elements...

So we finally got to test this and it appears to work and esIndexCleaner works. BUT... This breaks spark. It will throw an error stating that it only supports version...

Yeah I'll give it a go tomorrow. I'm just using the default from the chart. If that works then I guess the chart needs updating. This is pulling the image...

going to close this issue and keep the spark part in a different issue

We use esIndexCleaner regularly with no issue out of the box. Like this: ```yaml jaeger: esIndexCleaner: enabled: true schedule: "55 23 * * *" resources: requests: cpu: 256m memory: 128Mi...

I have found a more simple way to set this instead of the lifecycle hack on start... ```yaml collector: cmdlineParams: es.num-replicas: "0" ``` I am sure I can template that...

This problem also exists with Spark. It will default to setting replica count to 1 and then in kuberentes it will start as Yellow in elasticsearch and then fail to...