-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Update the OCI Provider to incorporate SoftError to avoid CrashLoopBackoff #4229
Merged
k8s-ci-robot
merged 1 commit into
kubernetes-sigs:master
from
jrosinsk:fix/oci-softerror
Feb 14, 2024
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
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.
I understand the use of
NewSoftError
for Get or List Records / ZonesHere, it's when patching zone record, so I have doubts.
Can we really be sure it won't have any unexpected side effect ?
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.
In this case, the new behavior is calling this a Fatal error right away. By wrapping this in a SoftError the previous expected behavior is restored. The new unexpected behavior would be to Fatal here. Doesn't it make more sense to have the pod in this case retry in an hour rather than crash the pod and have to recreate the Update immediately. I don't recall seeing external-dns pods being killed when updates failed.
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.
Basically, this change to return a Fatal error has already caused a major unexpected failure of external-dns pods across multiple regions in our tenancy. This has never happened before. So this change is trying to restore what was previous behavior to avoid getting bit by this again in a slightly different way.