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
make prober always sleep before execute #1908
Conversation
(args.deployment, args.zone, args.project)).split(' ')) | ||
util_run(("kubectl create -f %s" % SSL_DIR).split(' ')) | ||
|
||
return True |
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.
Should we use the retrying module rather than writing our own loop for retries?
The retrying module allows you to specify various conditions. Typically, I suggest retrying for up to some maximum amount of time with exponential backoff between retries.
Typically its best to specify a max duration for retries e.g. we will give up after X minutes; because that makes it easier to reason about.
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.
updated
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jlewi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
* make prober always sleep before execute * use retry modules
* common: Upgrade to Istio 1.9.5 Signed-off-by: Yannis Zarkadas <yanniszark@arrikto.com> * common: Fix all references to new Istio 1.9.5 Signed-off-by: Yannis Zarkadas <yanniszark@arrikto.com>
kubectl create
exception when it happensThis change is