When I call scaffold run in the examples/helm-deployemnt directory it should deploy.
UPGRADE FAILED: "skaffold-helm" has no deployed releases
This issue was already raised and marked as 'closed' - it still persists!
Workaround:
deploy:
...
flags:
upgrade:
- --install
this could be related to #3400.
I was not able to re-produce this at my end. @SakrImpargo can you try the upgrade flag mentioned above to see if it fixes the issue.
For helm2, the command syntax is helm get RELEASE-NAME
https://v2.helm.sh/docs/helm/#helm-get
It corresponds to this line.
https://github.com/GoogleContainerTools/skaffold/blob/release/v1.1.0/pkg/skaffold/deploy/helm.go#L186
For helm3, the command syntax changed.
$ helm get --help
...
Usage:
helm get [command]
Available Commands:
all download all information for a named release
hooks download all hooks for a named release
manifest download the manifest for a named release
notes download the notes for a named release
values download the values file for a named release
...
What's more, helm get RELEASE-NAME doesn't return any error.
$ helm get skaffold-helm >/dev/null
$ echo $?
0
Therefore, isInstalled remains true and goes into this block.
https://github.com/GoogleContainerTools/skaffold/blob/release/v1.1.0/pkg/skaffold/deploy/helm.go#L207-L216
Yes that's exactly the issue. I explored this a bit here: https://github.com/GoogleContainerTools/skaffold/issues/3400#issuecomment-568243536
Workaround:
deploy: ... flags: upgrade: - --install
is this the recommended workaround in the meantime?
is this issue still present without the workaround?
I believe this was addressed by the helm3 improvements in recent releases. Please /reopen if not.
For broken deployments, try deleting the helm release, even if the release doesn't show up in listing.
$ helm delete <release>
If this helps someone else, I think this happened when a skaffold debug ... with a helm deployer was interrupted with ctrl-C maybe twice and the helm uninstall didn't complete.
Running helm list --all-namespaces didn't show it but a helm list --all-namespaces -a did show that it was in an "uninstalling" state.
Runninig helm delete -n ns release-name cleared it up as mentioned by @smrutimandal
Most helpful comment
Workaround: