This repository has been archived by the owner on Feb 9, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 109
Tracking: dns-app update timeout may not be long enough #2282
Labels
Comments
Example log of a suspexted failure that is related... from the dns update job
|
This was referenced Nov 13, 2020
Merged on each release branch, pending releases. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
What happened:
Under high scheduler load / long scheduling delays, it appears possible that the coredns upgrade can timeout before the new pods have been scheduled. We need to validate/double check the timers on the dns-app upgrades are long enough to tolerate longer than expected scheduling from kubernetes.
The text was updated successfully, but these errors were encountered: