indexes created by jaeger collector not linked to jaeger-span template hence not following index lifecycle policy

Hello,
I am trying to troubleshoot a data retention issue for our jaeger-span-* indexes.
This is a pre-existing installation that I parachuted into so I apologize of I can't provide all the details.

The indexes jaeger-span-YYYY-MM-dd and jaeger-service-YYYY-MM-dd are created daily by our jaeger operator running on kubernetes.
The jaeger operator was deployed using a helm chart from Jaeger documentation

I created a jaeger-retention ILM to delete indexes older than x days.
I linked the ILM to the jaeger templaes jaeger-service and jaeger-span
which have index patterns jaeger-service-* and jaeger-span-* respectively. I dont know how the jaeger-span and jaeger-template were created (if by the jaeger-operator at start up or manually)

What I am noticing is that the indexes (ie jaeger-span-2024-12-02) dont seem to be mapped to the templates and that could be the reason why they are not being linked to the jaeger-retention ILM.

Hope this makes sense.

Jose