helm list -n <namespace> doesn't give accurate output

[kaajrot]

Describe the bug a clear and concise description of what the bug is.

We use the spec targetNamespace for some of our helm releases to install them in a particular namespace. but the release shows up when we query kube-infrastructure namespace.

ex- helm list -n kube-infrastructure should list only the releases installed under namespace kube-infrastructure. But we get some that are installed in different namespaces.

What's your helm version?

version.BuildInfo{Version:"v3.9.0", GitCommit:"7ceeda6c585217a19a1131663d8cd1f7d641b2a7", GitTreeState:"clean", GoVersion:"go1.18.2"}

What's your kubectl version?

Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.2", GitCommit:"f66044f4361b9f1f96f0053dd46cb7dce5e990a8", GitTreeState:"clean", BuildDate:"2022-06-15T14:14:10Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"darwin/amd64"}

What's the chart version?

flux2-0.20.0

What happened?

helm list -n kube-infrastructure list helmreleases that are not installed in kube-infrastructure namespace.

What you expected to happen?

helm list -n kube-infrastructure should list only helmreleases that are installed in kube-infrastructure namespace.

Enter the command that you execute and failing/misfunctioning.

helm list -n kube-infrastructure

[kaajrot]

Hello @stefanprodan, could you tag the other developers so that we could get some assistance here?

[hiddeco]

What is the storageNamespace and targetNamespace you have configured on the said release?

[kaajrot]

We do not have storageNamespace configured for our release.

example:

metadata:
  name: rasa-x
  namespace: kube-infrastructure
spec:
  targetNamespace: mal-development

[stefanprodan]

You need to set the storageNamespace to the same value as targetNamespace for Helm CLI to work, the Helm CLI is not as flexible as Flux and expects the storage and the release to be in the same namespace.