mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-22 12:43:32 +09:00
Redis and Sentinel read tls-cert-file and tls-key-file once at startup, so a leaf renewed by cert-manager 30 days before its one-year expiry is served only after the pods restart. The operator does that restart: on every reconcile it reads the TLS Secret and stamps a hash of tls.crt and ca.crt into the pod template of the Redis StatefulSet and the Sentinel Deployment, so a renewal rolls Redis through the operator's own roller (the StatefulSet is OnDelete; the roller replaces one pod per reconcile, replicas before the master) and Sentinel through its Deployment. The TLS section presented the setup as turnkey and said nothing about renewal. Say what happens, and name the fallback: when the roll cannot run, because the operator is down or its reconcile of this RedisFailover keeps failing, the deadline is the old certificate's expiry, since past it the operator's own TLS connections to Sentinel and Redis fail along with the clients. The CA has a clock of its own: five years, reissued on the same key before the end, so a ca.crt copied once verifies new leaves only until the original CA certificate expires. Say that too, and point at re-reading the projection instead of baking the copy in. A stakater reloader annotation is not an alternative here and is not used: the operator regenerates the pod template on every reconcile, so nothing written into it from outside survives to the next one. Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Aleksei Sviridkin <f@lex.la>