This repository has been archived by the owner on Feb 9, 2024. It is now read-only.
Increase dns-app update status checks #2324
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The number of retry attempts when checking the status of rigging changes may be too short for clusters experiencing high scheduler load. We have a customer app that appears to crash during the app update, creating lots of kubernetes scheduler events and the dns pods can take more than 2 minutes to start.
UnderGreen
approved these changes
Nov 13, 2020
bernardjkim
approved these changes
Nov 13, 2020
knisbet
pushed a commit
that referenced
this pull request
Nov 15, 2020
The number of retry attempts when checking the status of rigging changes may be too short for clusters experiencing high scheduler load. We have a customer app that appears to crash during the app update, creating lots of kubernetes scheduler events and the dns pods can take more than 2 minutes to start. (cherry picked from commit 2fd474a)
knisbet
pushed a commit
that referenced
this pull request
Nov 15, 2020
The number of retry attempts when checking the status of rigging changes may be too short for clusters experiencing high scheduler load. We have a customer app that appears to crash during the app update, creating lots of kubernetes scheduler events and the dns pods can take more than 2 minutes to start. (cherry picked from commit 2fd474a)
knisbet
pushed a commit
that referenced
this pull request
Nov 15, 2020
The number of retry attempts when checking the status of rigging changes may be too short for clusters experiencing high scheduler load. We have a customer app that appears to crash during the app update, creating lots of kubernetes scheduler events and the dns pods can take more than 2 minutes to start. (cherry picked from commit 2fd474a)
knisbet
pushed a commit
that referenced
this pull request
Nov 15, 2020
The number of retry attempts when checking the status of rigging changes may be too short for clusters experiencing high scheduler load. We have a customer app that appears to crash during the app update, creating lots of kubernetes scheduler events and the dns pods can take more than 2 minutes to start. (cherry picked from commit 2fd474a)
This was referenced Nov 15, 2020
knisbet
pushed a commit
that referenced
this pull request
Nov 17, 2020
* Increase dns-app update status checks (#2324) The number of retry attempts when checking the status of rigging changes may be too short for clusters experiencing high scheduler load. We have a customer app that appears to crash during the app update, creating lots of kubernetes scheduler events and the dns pods can take more than 2 minutes to start. (cherry picked from commit 2fd474a) * Bump DNS_APP_TAG
knisbet
pushed a commit
that referenced
this pull request
Nov 17, 2020
* Increase dns-app update status checks (#2324) The number of retry attempts when checking the status of rigging changes may be too short for clusters experiencing high scheduler load. We have a customer app that appears to crash during the app update, creating lots of kubernetes scheduler events and the dns pods can take more than 2 minutes to start. (cherry picked from commit 2fd474a) * Update Makefile
knisbet
pushed a commit
that referenced
this pull request
Nov 18, 2020
* Increase dns-app update status checks (#2324) The number of retry attempts when checking the status of rigging changes may be too short for clusters experiencing high scheduler load. We have a customer app that appears to crash during the app update, creating lots of kubernetes scheduler events and the dns pods can take more than 2 minutes to start. (cherry picked from commit 2fd474a) * Bump DNS_APP_TAG
helgi
pushed a commit
to helgi/gravity
that referenced
this pull request
Jun 21, 2021
The number of retry attempts when checking the status of rigging changes may be too short for clusters experiencing high scheduler load. We have a customer app that appears to crash during the app update, creating lots of kubernetes scheduler events and the dns pods can take more than 2 minutes to start.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The number of retry attempts when checking the status of rigging changes may be too short for clusters experiencing high scheduler load. We have a customer app that appears to crash during the app update, creating lots of kubernetes scheduler events and the dns pods can take more than 2 minutes to start.
Update the retry attempts to allow for ~10 minutes.
Type of change
Linked tickets and other PRs
Updates #2282
TODOs