stefanprodan
commented
2 years ago This is the wrong org to report Flux issue. Flux is being developed under the fluxcd org. This issue should be opened in fluxcd/helm-controller repo.
Closed kaajrot closed 2 years ago
stefanprodan
commented
2 years ago This is the wrong org to report Flux issue. Flux is being developed under the fluxcd org. This issue should be opened in fluxcd/helm-controller repo.
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.
How to reproduce it?
No response
Enter the changed values of values.yaml?
No response
Enter the command that you execute and failing/misfunctioning.
helm list -n kube-infrastructure
Anything else we need to know?
No response