Is there a concept/process for restarting the controller or reloading it to pick up a new cert?
Assuming you’re not using a self signed cert, and you have shorter lifetimes than a year we need to be able to rotate the cert quite often and restarting the service seems rather extreme?
There has been internal work to support such features in a generic capacity in shared libraries, but it hasn’t surfaced in all places. It would only support file:<path> configurations in its current form. Hardware-backed storage would need its own engine-backed implementation that has not been investigated. Additionally, mutating <pem>:<pem-cert/pem-key> is not currently supported. The goal was mainly aimed at routers and alternative server certificates. There are caveats and sharp edges to what you are asking about. I have a few questions if you don’t mind:
Are you rotating the server_cert, cert, and/or alt_server_certs (defined here)
Sorry @pixitha … Holiday season and it’s easy to miss following up… @andrew.martinez is out at least till tomorrow. Thanks for the bump. I’ll try to grab his attention on this one too.
FWIW, the process of restarting routers and controller is “very fast” so most likely, humans would never even notice a restart blip. That said, it’d certainly be friendly if the server just recognized the certs change and reloaded 'em.