community
community copied to clipboard
Add retry & backoff strategy to late initialization config
As part of feedback on PR #849 , Add retry-backoff strategy for late initialization of server side defaults.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle rotten
/remove-lifecycle rotten
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/aws-controllers-k8s/community.
/lifecycle stale
/lifecycle frozen
Reviewed and assigned for consideration.
/close
Haven't needed this feature for a number of years and have partially implemented with SkipIncompleteLateInitization flags. Will re-open or create new issue if needed.
@knottnt: Closing this issue.
In response to this:
/close
Haven't needed this feature for a number of years and have partially implemented with SkipIncompleteLateInitization flags. Will re-open or create new issue if needed.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.