-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sync change from Klutch upstream #35
Merged
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
abdulhaseeb3
requested review from
mkfdoherty,
iliasmavridis,
jcartossa,
rfashwall-anynines and
m-hofmann-a9s
as code owners
January 7, 2025 08:08
abdulhaseeb3
force-pushed
the
sync-changes
branch
5 times, most recently
from
January 10, 2025 12:34
5bc1534
to
a700881
Compare
Our confighealth reconciler performs a health check HTTP request to the anynines service broker and writes the result to the providerconfig's status field. Previously, one Golang context with a timeout was used for both the health check and the subsequent patching of providerconfig's status. However, if the health check request exceeded the timeout, the patching of the status field could never succeed. client-go's Patch() method would error with a "context deadline exceeded" error message. This commit introduces a separate sub-context for the health check request, which has an explicit timeout, while using the parent context (which does not time out) for patching the status field.
abdulhaseeb3
force-pushed
the
sync-changes
branch
from
January 14, 2025 10:08
a700881
to
77f4b42
Compare
abdulhaseeb3
force-pushed
the
sync-changes
branch
from
January 14, 2025 10:48
f50f8ad
to
0b043f5
Compare
rfashwall-anynines
approved these changes
Jan 15, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
WARNING: Only users listed in the CODEOWNERS file can approve PRs!