Critical Create and E2E test to check we don't add regressions for this upstream issue:
When .spec.storage.options.es.tls.enabled is true, the flag is not passed properly to the index cleaner job. This makes the job fail because other flags related to TLS are enabled and this situation is incompatible:
> kubectl logs jaeger-instance1-es-index-cleaner-1653346500-9zsp2 -n instance1 Error: es.tls.* options cannot be used when es.tls.enabled is false Usage: jaeger-es-index-cleaner NUM_OF_DAYS http://HOSTNAME:PORT [flags] Flags: --archive Whether to remove archive indices. It works only for rollover --es.password string The password required by storage --es.tls.ca string Path to a TLS CA (Certification Authority) file used to verify the remote server(s) (by default will use the system truststore) --es.tls.cert string Path to a TLS Certificate file, used to identify this process to the remote server(s) --es.tls.enabled Enable TLS when talking to the remote server(s) --es.tls.key string Path to a TLS Private Key file, used to identify this process to the remote server(s) --es.tls.server-name string Override the TLS server name we expect in the certificate of the remote server(s) --es.tls.skip-host-verify (insecure) Skip server's certificate chain and host name verification --es.username string The username required by storage -h, --help help for jaeger-es-index-cleaner --index-date-separator string Index date separator (default "-") --index-prefix string Index prefix --rollover Whether to remove indices created by rollover --timeout int Number of seconds to wait for master node response (default 120) 2022/05/23 22:55:22 es.tls.* options cannot be used when es.tls.enabled is false