Certificate Hot Reload is not happening for the ZIPKIN interface #6515
-
Hi @yurishkuro, Do we need to configure any CLI flag for the hot reload of server certificate in case of the zipkin interface in Jaeger v1.62.0? Was there certificate reload support for zipkin before v1.62.0? The reload is working after adding --collector.zipkin.tls.reload-interval cli flag. Could you please mention about this flag in https://www.jaegertracing.io/docs/1.62/cli/? Thanks, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
I couldn't find specific information about TLS certificate hot reload for the Zipkin interface in Jaeger v1.62.0. However, there is a similar unsolved discussion regarding missing CLI flags for TLS reload in the Jaeger documentation, which might be related to your issue. You can view the discussion here [1]. For other interfaces, the general CLI flag for TLS certificate hot reload is To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
Beta Was this translation helpful? Give feedback.
I couldn't find specific information about TLS certificate hot reload for the Zipkin interface in Jaeger v1.62.0. However, there is a similar unsolved discussion regarding missing CLI flags for TLS reload in the Jaeger documentation, which might be related to your issue. You can view the discussion here [1].
For other interfaces, the general CLI flag for TLS certificate hot reload is
--<prefix>.tls.reload-interval
, which specifies the duration after which the certificate will be reloaded. This flag is available ifEnableCertReloadInterval
is set to true in theServerFlagsConfig
[2][3].To continue talking to Dosu, mention @dosu.
Help Dosu learn! Give it feedback: Great Response | Irrele…