When Redpanda Console is deployed on Kubernetes with mTLS and cert-manager for automatic certificate rotation, the Console loses connection to the Redpanda cluster after certificate renewal because it doesn't hot reload the new certificate.
We are deploying RedPanda Console on Kubernetes connecting to a RP cluster with mTLS authentication enabled. The Console is deployed with the RP helm chart (standalone, not as subchart of main redpanda chart) and the mTLS admin certificate is provided as a Secret mounted as file in the console pod. We are using cert-manager to handle automatic certificate rotation, after automatic renewal due to certificate expiration the Console is not able to "talk" to RedPanda anymore, even though the TLS cert/keys are correctly updated in the pod by Kubernetes. This results on a downtime of the console.