In some cases it would be nice it Centauri lazy-requested the certificate when the route was first hit, rather than immediately at start up, to stagger an initial wave of certificate requests rather than risking hitting rate limits.
I'm unsure how best to handle renewals - renew as normal or lazy-renew (only renew if it's if's hit within X days of renewal being due or it's expired)
In some cases it would be nice it Centauri lazy-requested the certificate when the route was first hit, rather than immediately at start up, to stagger an initial wave of certificate requests rather than risking hitting rate limits.
I'm unsure how best to handle renewals - renew as normal or lazy-renew (only renew if it's if's hit within X days of renewal being due or it's expired)