-
Notifications
You must be signed in to change notification settings - Fork 55
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 clean project timeout configurable #328
Comments
mchoma
pushed a commit
to mchoma/xtf
that referenced
this issue
Jan 7, 2020
mchoma
pushed a commit
to mchoma/xtf
that referenced
this issue
Jan 8, 2020
mchoma
pushed a commit
to mchoma/xtf
that referenced
this issue
Jan 8, 2020
mchoma
pushed a commit
to mchoma/xtf
that referenced
this issue
Jan 8, 2020
mchoma
pushed a commit
to mchoma/xtf
that referenced
this issue
Jan 8, 2020
Crumby
pushed a commit
that referenced
this issue
Jan 8, 2020
Fixed by #329 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently it is hardcoded to 20 seconds.
There are scenarios where it is necessary to wait longer. Since Kubernetes 1.16 (OCP 4.3) by default Service of type LoadBalancer waits until cloud providers load balancer resource is cleaned up [1]. On AWS 20 seconds is sometimes not enough.
[1] https://v1-16.docs.kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#garbage-collecting-load-balancers
The text was updated successfully, but these errors were encountered: