[Bug]: jaeger-chart: does not exist .Values.storage.elasticsearch.tls in es-rollover-hook.yml

[obervinov]

What happened?

Description es-rollover-hook.yml template does not support the .Values.storage.elasticsearch.tls settings, as implemented for example in es-rollover-cronjob.yaml.

This creates a situation where rollover-hook-init cannot be used with a custom CA configured via parameters storage.elasticsearch.tls, as it will fall with an error of the missing certificate installed in ES_TLS_CA.

If you try to use parameter .Values.esRollover.extraSecretMounts, it causes a conflict with the environment variable ES_TLS_CA.

The only option left is not to use parameter .Values.storage.elasticsearch.tls, but to manually declare extraSecrets and extraEnvs for each chart microservice.

I would like to correct this situation with a small edit.

Steps to reproduce

1. Set these values for the jaeger chart

   
   storage:
   type: elasticsearch
   elasticsearch:
   scheme: https
   host: es-node-1.example.com
   tls:
     enabled: true
     secretName: intermidiate-ca-certificate

esRollover: enabled: true extraEnv:

• name: CONDITIONS value: '{"max_age": "1d"}' schedule: "40 14 *" successfulJobsHistoryLimit: 1 failedJobsHistoryLimit: 1 concurrencyPolicy: Forbid

  
  2. Install this helm chart
  3. Get an error

Expected behavior

The .Value.storage.elasticsearch.tls parameter automatically adds the mounting of the specified Secret to the executed es-rollover-hook.yml just as in the template es-rollover-cronjob.yaml

Relevant log output

Error: failed to load CA CertPool: failed to load CA /es-tls/ca-cert.pem: open /es-tls/ca-cert.pem: no such file or directory

Screenshot

Additional context

No response

Jaeger backend version

v1.43

SDK

No response

Pipeline

No response

Stogage backend

Elasticsearch

Operating system

Linux

Deployment model

Kubernetes

Deployment configs

No response