Increase default provisioner, resizer, snapshotter retry-interval-max #820
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
outscale-hmi
force-pushed
the
retryIntervall
branch
from
503e224 to
68bf799
Compare
Signed-off-by: hanenMizouni <[email protected]>
outscale-hmi
force-pushed
the
retryIntervall
branch
from
68bf799 to
1c22cbc
Compare
outscale-mdr
approved these changes
Oct 1, 2024
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.
Is this a bug fix or adding new feature?
Improvement
What is this PR about? / Why do we need it?
Today, the max backoff period for any sidecar RPC is 5 minutes. This is problematic if the user has a misconfigured K8s object (such as invalid IOPS for volume type) because the invalid request will be retried every 5 minutes until user resolves the issue.