The only Helm repo that is available in the Helm Chart explorer is the OpenShift Helm repo, even if the user has configured additional ones outside of VS Code OpenShift. This is a problem, since many of the charts in the OpenShift Helm repo (including most of the interesting ones like Postgres, Redis, and Jenkins) only work on OpenShift, since they rely on Routes or DeploymentConfigs.
In order to get the extension to work better with other Kubernetes clusters, I think that we should:
- Show all the charts from all the Helm repos that the user has configured in the Helm chart explorer webview
- Add some sort of indicator, perhaps a small chip, to show which charts come from which repo
- Add a list of checkboxes in the Helm chart explorer to show/hide charts for a particular repo
There is a mechanism to add/remove Helm repositories in the Kubernetes extension, so I don't think we need to do that as part of this issue.
The only Helm repo that is available in the Helm Chart explorer is the OpenShift Helm repo, even if the user has configured additional ones outside of VS Code OpenShift. This is a problem, since many of the charts in the OpenShift Helm repo (including most of the interesting ones like Postgres, Redis, and Jenkins) only work on OpenShift, since they rely on Routes or DeploymentConfigs.
In order to get the extension to work better with other Kubernetes clusters, I think that we should:
There is a mechanism to add/remove Helm repositories in the Kubernetes extension, so I don't think we need to do that as part of this issue.