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
After a temporary proxy/auth server downtime, node's /readyz endpoint reports "recovering" state for up to 10min.
The problem is that the current readyz state is updated via certificate rotation checks, which happen every 10min. It should instead be tied to heartbeats, that happen way more frequently.
What you expected to happen:
Node should recover in <1m after proxy/auth server come back online.
The text was updated successfully, but these errors were encountered:
Description
What happened:
After a temporary proxy/auth server downtime, node's
/readyz
endpoint reports "recovering" state for up to 10min.The problem is that the current readyz state is updated via certificate rotation checks, which happen every 10min. It should instead be tied to heartbeats, that happen way more frequently.
What you expected to happen:
Node should recover in <1m after proxy/auth server come back online.
The text was updated successfully, but these errors were encountered: