Let's say you create a Helm release called my-janus, based on the backstage Helm chart from the OpenShift Helm repository:
It will appear in the "Application Explorer" panel as my-janus-backstage:
If you attempt to use the context menu to uninstall the Helm release:
Then nothing happens.
This is because the command is trying to uninstall the release my-janus-backstage, but the release is called my-janus. However, if you name the release my-janus-backstage, then the uninstall works.
The root cause is that the item that appears in the "Application Explorer" isn't the Helm release, it's a deployment created by the Helm chart, which is only one of the components making up the Helm release. In order to address this issue, we should list Helm releases in the "Application Explorer" tree view.
You can run helm list -o json to get a JSON list of the Helm releases for the current namespace.
Let's say you create a Helm release called
my-janus, based on thebackstageHelm chart from the OpenShift Helm repository:It will appear in the "Application Explorer" panel as
my-janus-backstage:If you attempt to use the context menu to uninstall the Helm release:
Then nothing happens.
This is because the command is trying to uninstall the release
my-janus-backstage, but the release is calledmy-janus. However, if you name the releasemy-janus-backstage, then the uninstall works.The root cause is that the item that appears in the "Application Explorer" isn't the Helm release, it's a deployment created by the Helm chart, which is only one of the components making up the Helm release. In order to address this issue, we should list Helm releases in the "Application Explorer" tree view.
You can run
helm list -o jsonto get a JSON list of the Helm releases for the current namespace.