You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presently, the deployments for Linux and Docker renew the controller's leaf certs at startup by default. Clint suggests in this comment that they should also or instead renew the leaf certs at some interval.
If they did renew at an interval, it would be better than requiring a restart of the controller, especially if only one controller existed.
The best way to address this is by discussing how the controller should manage its certificates. That would be better than requiring every deployment to wrap and manage leaf cert renewal.
The text was updated successfully, but these errors were encountered:
Presently, the deployments for Linux and Docker renew the controller's leaf certs at startup by default. Clint suggests in this comment that they should also or instead renew the leaf certs at some interval.
If they did renew at an interval, it would be better than requiring a restart of the controller, especially if only one controller existed.
The best way to address this is by discussing how the controller should manage its certificates. That would be better than requiring every deployment to wrap and manage leaf cert renewal.
The text was updated successfully, but these errors were encountered: