feat(k8s): introduce several retry functions to deal w/ flaky apis #1219
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
To deal with flaky kube-apiservers we wrote several retry functions. Related issue: aws/containers-roadmap#1810 (comment)
I am unsure whether these functions will be considered, but it was little effort to make a PR.
TODOs
Read the Gruntwork contribution guidelines.
Release Notes (draft)
Added k8s functions:
RunKubectlWithRetry
,RunKubectlWithRetryE
,RunKubectlAndGetOutputWithRetry
,RunKubectlAndGetOutputWithRetryE
,KubectlApplyFromStringWithRetry
,KubectlApplyFromStringWithRetryE
Migration Guide
N/A