dayeguilaiye
dayeguilaiye
This could be very useful for me too!
IMO, from the perspective of Helm as a deployment tool, Helm only needs to display the resources included in the manifest, without needing to worry about whether these resources exist...
一样的错误，请问有进展吗？或者是否有规避方法？ @Chen-jj @luckyadam
@mattfarina I've reproduced this issue. 1. Execute `helm install testChart /path/to/chartv1 --wait --timeout=10s`, chartv1 looks like below, and command success. - a normal deployment - a configmap with `"helm.sh/resource-policy": keep`...
@gjenkins8 Yes, I found the code too, and the code is the reason why this problem happened. After send patch request to k8s, helm will check `isPodReady` immediately. But the...
@antoineozenne-at-leocare helm can wait for deployment and jobs correctly. If you want helm to wait for deployment, you should run with `--wait` flag. But if you want it wait for...
This seems not a bug to me, maybe the request of updating resources already been sent to k8s, so the pod become healthy after cancel helm `RunWithContext` is reasonable. The...
@jmorganca I have the same problem now in 0.5.7. I think this problem may not be solved yet. This issue should be opened.
@joejulian That's right, I will add a check before add it to array. And add unit tests for it and for this condition.
@joejulian I've added the check and unit test, please check if it's OK