Better namespace support

[dzavalkinolx]

Current namespace support in helm is not a way to go. I should see only charts from current namespace (like I do with kubectl get xxx commands) and/or namespace name when I run helm list. Currently I see all helm charts installed in this cluster.

[hyperfocus1337]

Current way to switch to a different namespace in kubectl is kubectl config set-context dev --namespace=development --cluster=cluster --user=cluster

Maybe

helm config set-context dev

To switch? Would be nice.

[mgoodness]

Duplicate/variation of #1563?

[technosophos]

There's a little bit of terminological confusion that might be happening here.

When a Helm chart is installed, it creates a release. A release is not bound to a namespace. (That's why a release itself can contain a namespace definition). In fact, it should be possible (though I can't say I've personally tried) to deploy a single chart that creates multiple objects in multiple namespaces.

For that reason, it doesn't necessarily make sense to say that releases should be constrained to "their namespaces", as they are not namespaced objects.

That's also part of the reason why nothing's really been done on #1563. However, that issue does at least give us one way forward: We could apply filters that would only return releases that had objects in a particular namespace.

Edit: To further clarify, I think the confusion stems from the --namespace flag on install/upgrade, which sets the base namespace that is used during the release. This flag does not mean that the release itself is installed into a namespace. It just sets the namespace used by namespaced objects (pods, rs/rc/deployment, etc). But I do see where the confusion stems from.

[technosophos]

I am going to close this in favor of #1563, which is on the docket for Helm 2.2.0. After re-reading this and that issue, I think we may try to support a general filter syntax based on metadata like label selectors, name, and namespace.