You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since a few weeks, I've discovered an issue with the --wait feature. I've
checked with the existing issues but there all seem to be closed or not exactly
what I encountered.
For some reasons, even with the --wait (or --atomic) arg, helm will not wait
until the resources are ready (not even created sometimes). The issue happens
most of the time but not always :/ I happens with the install and upgrade
command. Also an interesting fact, the issue seems to only appear with large
docker images (> 400 MB).
I've tested with multiple helm versions, listed here:
- 3.2.4
- 3.4.2
- 3.5.4
- 3.7.2
- 3.9.1
- build from source from #10920
K8S version: v1.21.9 deployed using RKE1 (from Rancher)
This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs.
Hello,
Since a few weeks, I've discovered an issue with the
--wait
feature. I'vechecked with the existing issues but there all seem to be closed or not exactly
what I encountered.
For some reasons, even with the
--wait
(or --atomic) arg, helm will not waituntil the resources are ready (not even created sometimes). The issue happens
most of the time but not always :/ I happens with the
install
andupgrade
command. Also an interesting fact, the issue seems to only appear with large
docker images (> 400 MB).
I've tested with multiple helm versions, listed here:
- 3.2.4
- 3.4.2
- 3.5.4
- 3.7.2
- 3.9.1
- build from source from #10920
K8S version: v1.21.9 deployed using RKE1 (from Rancher)
Helm command:
Here are the manifests I got using
helm template
:Manifests
Let me know if you need anything else :)
The text was updated successfully, but these errors were encountered: