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
werf helm upgrade with atomic flag and timeout #5550
Labels
Comments
@AdamMachera Hi! Looks like in your case werf's default failure detector fires a readiness-probe-error:
— thus it fails deploy process before timeout event occurs. To alter default failure detector behaviour there are some annotations, which could be specified into the target resource:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Before proceeding
Version
v1.2.214+fix3
How to reproduce
Have a pod that is a part of helm package that takes 10minutes to start.
Run helm upgrade --install with --timeout 15m and --atomic set
Result
I wanted to add some insights into my werf helm upgrade.
I have --atomic and --timeout 15m set.
If I'm running it without werf it finished around 10m.
Operation start:
Operation end:
Process has run for 8minutes. Any idea why
At the end before rollback I see this
Expected result
Werf takes into account --timeout flag when working with helm
Additional information
No response
The text was updated successfully, but these errors were encountered: