[Jaeger] Add a batch job to clean up ElasticSearch indices about helm-charts

[naseemkullah]

Sounds good @mehta-ankit , let's use the cronjob if that's what the operator does. It seems to run es-curator in any case.

[vkasu-dojo]

It would be very helpful if we can add support for passing ES_USERNAME & ES_PASSWORD similar to collector deploy and spark cronjob?

[vkasu-dojo]

@naseemkullah Raised a PR #65 for adding ES_USERNAME and ES_PASSWORD environment variable to the jaeger-es-index-cleaner job.

[mehta-ankit]

Also, if we end up deciding on a CronJob, i already have one for my purposes that i am using and can make a PR with that. 👍

[mehta-ankit]

This PR addresses this issue: #60

[mehta-ankit]

@naseemkullah Should we just close this issue ?

[mehta-ankit]

@naseemkullah Thoughts ?

[naseemkullah]

That's a great point, we could allow for the creation of https://github.com/helm/charts/tree/master/stable/elasticsearch-curator as a subchart or use the recommended practice of ILM which would be configured in whatever manner the elastic chart recommend. But IMHO there should be no additional template to this jaeger chart.

[naseemkullah]

On second thought, if jaeger are maintaining an image specifically for this, perhaps we could indeed add it as a cronjob. 🤔

@jpkrohling @yurishkuro Is there a reason operator does not recommend using elastic curator or built int ILM of elasticsearch for index deletion, but resort to a custom tool?

[naseemkullah]

Yep! Solved via #60

[naseemkullah]

💯 @venukasu Would you be willing to make a PR to add this?