Hello Folks,
I have telegraf running as a pod using a client certificate which expires every 1 hour. this cert is mounted as secret to my telegraf deployment. telegraf sends the metrics using http output plugin to envoy based proxy where the client cert validation and TLS termination occurs.
I’m observing the following behaviour
- when the cert rotates the secret is updated and the same is visible in the container file system
- For some reason, the proxy pod is restarted, the flow of metrics from telegraf to proxy is interrupted with expired cert error
- at this point, the certs in the secret mounted on telegraf is updated with a valid cert, the cert is also reflected in the container file system
The only path forward seems to be to restart telegraf pod. Is there a way to force telegraf to reset the connection or is there a better way of handling this instead of restarting the pod.
