Unable to view Helm details when storage and installation namespace differ #372
Description
We are using Flux to manage most of our Helm Releases. The releases themselves are "stored" in one namespace (the Secret type=helm.sh/release.v1) while they are installed to various target namespaces. In Flux's (default) multi-tenant mode, the storage namespace defaults to the same namespace you are using for your Flux resources.
As a result, all of our releases are stored in a namespace called cluster-config but the actual target/installation namespace varies. For example, I have a chart Ak2k8s which is installed in the akv2k8s namespace but stored by Helm in a Secret in the cluster-config namespace.
If I select "all namespaces" when viewing Releases, I will see each Helm release and the namespace column will accurately reflect the installation namespace. If I select that namespace instead, the release is missing which is expected. If I select the storage namespace I see a list of all the releases again. So far so good.
The problem comes when I actually click on one of the releases to view their manifests / values. The "Resources" tab just displays a blank/collapsed section. Clicking on "View", "Manifest", "Notes" or "Values" shows a loading screen that never actually loads. Clicking on "History" returns an error:
exit status 1: Error: release not found
If I run helm get all akv2k8s --namespace cluster-config or helm history akv2k8s --namespace cluster-config I am returned the expected results.
I suspect that Kubernetic is not able to understand the difference between the target namespace and the storage namespace and as a result just hangs trying to load the data from Helm. But that's just a guess. I'm happy to help debug if there's a way to gather any useful information.