trace deploy looks in different projects

[jkroepke]

Hi!

running kubespy trace deploy internal-tiller/tiller shows me this output:

[ADDED extensions/v1beta1/Deployment]  internal-tiller/tiller
    Rolling out Deployment revision 3
    ✅ Deployment is currently available
    ✅ Rollout successful: new ReplicaSet marked 'available'

ROLLOUT STATUS:
- [Current rollout | Revision 3] [ADDED]  joe-helm-test/tiller-877613549
    ✅ ReplicaSet is available [0 Pods available of a 0 minimum]

- [Previous ReplicaSet | Revision 2] [ADDED]  testproject/tiller-7c58fdf799
    ⌛ Waiting for ReplicaSet to scale to 0 Pods (1 currently exist)

I wounder why there are reference to testproject or joe-helm-test while I just looking the tiller inside internal-tiller.

Running v0.4.0 on a mac running against our kubernetes 1.10 cluster.

[GJKrupa]

I'm seeing what's most likely a related issue. I'm accessing a cluster has rbac enabled restricting access to specific namespaces and preventing the use of --all-namespaces. When I try to use this feature I'm just getting the following error:

$ kubespy trace deploy my-namespace/my-deployment
unknown (get replicasets.extensions)

Presumably this is because watch.ObjectsOwnedBy() only takes a resource name parameter and not the namespace so it's querying all namespaces for matching resources (which isn't permitted in my case).

[jkroepke]

(which isn't permitted in my case)

Running also RBAC enabled but I'm a cluster admin.