[Bug]: Not able to set ES timeout when installing Jaeger using operator

[kunalmehta-eve]

What happened?

I am using this Jaeger definition to install the JAEGER after installing operator in cluster

apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
name: my-jaeger
namespace: monitoring
spec:
strategy: production
collector:
maxReplicas: 2
resources:
limits:
cpu: 100m
memory: 128Mi
storage:
type: elasticsearch
esIndexCleaner:
enabled: true
numberOfDays: 3
schedule: "45 23 * * *"
options:
es:
server-urls: https://elasticsearch-es-http.elastic-system:9200
index-prefix: jaeger
tls:
enabled: true
ca: /es/certificates/ca.crt
memory:
max-traces: 100000
secretName: elastic-credentials
volumeMounts:
- name: certificates
mountPath: /es/certificates/
readOnly: true
volumes:
- name: certificates
secret:
secretName: elasticsearch-es-http-certs-public
ingress:
enabled: false
agent:
strategy: DaemonSet
options:
log-level: debug
annotations:
scheduler.alpha.kubernetes.io/critical-pod: ""

I want to increase timeout for elastic search master for index cleaner, Please sugest

Steps to reproduce

Need help for configurations

Expected behavior

Need help for configurations, it should be able to add env variable in cleaner job pod for timeout

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

No response

Deployment configs