Referencing non-existent secret in Logzio-telemtetry chart

[gcpay-ci]

When installing the helm chart. This template references non-existent value in secret: https://github.com/logzio/logzio-helm/blob/cedf0956ebd787d350016d3c3a20ef7532b3aac9/charts/logzio-telemetry/templates/_pod.tpl#L92C17-L92C17

I installed the chart with those arguments (shipping keys are excluded from this snippet):

helm upgrade -n monitoring --create-namespace \
  --set logs.enabled=false \
  --set logzio-fluentd.secrets.logzioListener='listener.logz.io' \
  --set logzio-fluentd.env_id='dev' \
  --set metricsOrTraces.enabled=true \
  --set logzio-k8s-telemetry.metrics.enabled=true \
  --set logzio-k8s-telemetry.secrets.ListenerHost='https://listener.logz.io:8053' \
  --set logzio-k8s-telemetry.secrets.p8s_logzio_name='dev' \
  --set logzio-k8s-telemetry.enableMetricsFilter.eks=true \
  --set logzio-k8s-telemetry.traces.enabled=true \
  --set logzio-k8s-telemetry.secrets.LogzioRegion='us' \
  --set logzio-k8s-telemetry.spm.enabled=true \
  --set logzio-k8s-telemetry.secrets.env_id='dev' \
  --set logzio-k8s-telemetry.secrets.SamplingProbability='.004' \
  --set securityReport.enabled=true \
  --set logzio-trivy.env_id='dev' \
  --set logzio-trivy.secrets.logzioListener='listener.logz.io' \
  --set deployEvents.enabled=true \
  --set logzio-k8s-events.secrets.env_id='dev' \
  --set logzio-k8s-events.secrets.logzioListener='listener.logz.io' \
logzio-monitoring logzio-helm/logzio-monitoring

The helm chart install successfully, but the standalone deployment's container will not create a container:

    state:
      waiting:
        message: couldn't find key custom-tracing-endpoint in Secret monitoring/logzio-secret
        reason: CreateContainerConfigError

If I am not setting the custom endpoint value, this should not happen. There is likely some error in the chart's logic. You could track that down to fix that or you could set the optional field for the environment variable:

      {{ if .Values.secrets.CustomTracingEndpoint}}
      - name: CUSTOM_TRACING_ENDPOINT
        valueFrom:
          secretKeyRef:
            name: {{ .Values.secrets.name }}
            key: custom-tracing-endpoint
            optional: true
      {{ end }}

Let me know if you have any questions. This error isn't immediately obvious to you when installing the helm chart. If you don't describe the pod soon enough, the actual failure reason won't appear. I had to reinstall the deployment to see this error.