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
{{ message }}
This repository was archived by the owner on Nov 22, 2023. It is now read-only.
I think we only reload certs when we start a sync.
But if a client cert is invalid (eg, expired), there's no point in retrying with the same cert.
We saw this after a host had its renewal fail to happen on time, and then once we kicked the renewal, keysync still failed until it gave up retrying. We could have cut down the failure window here.
The text was updated successfully, but these errors were encountered:
TODO: If we do this all the time, it may increase server CPU as we'll make a
new TLS connection. So we might want something a bit smarter than this.
But it might fix some issues as outlined in Issue #83
I think we only reload certs when we start a sync.
But if a client cert is invalid (eg, expired), there's no point in retrying with the same cert.
We saw this after a host had its renewal fail to happen on time, and then once we kicked the renewal, keysync still failed until it gave up retrying. We could have cut down the failure window here.
The text was updated successfully, but these errors were encountered: