Fix namespace when watching (rather than getting) resources.

[absoludity]

Signed-off-by: Michael Nelson minelson@vmware.com

I just took a brief look at this issue after you mentioned @antgamdia it in the standup:

• The ResourceRef message already explicitly supports references for resources that are in other namespaces than the installed package context.
• The tests for the resources plugin already have a case for this.

but, that said, I wasn't able (yet) to test the streaming requests and as it turns out, it was using the installed package context namespace, rather than that of the resource.

This one-liner should fix it, though I'm keen to get the tests working for streaming requests to the fake k8s client too (need to add a watch reactor or something, which I think Greg may have done in some of his code already).

[antgamdia]

+1, though I did perform this same change yesterday with no luck. I think something else is failing, but still don't know what it is.
Edit: perhaps has sth to do with resourceRefsEqual, but I tried removing the namespace from the function, but still no success.

[antgamdia]

Good news, it seems it was a problem on my side (I wasn't fetching the k8s resources with the proper namespace).
Locally, with your changes and mine:

[absoludity]

Good news, it seems it was a problem on my side (I wasn't fetching the k8s resources with the proper namespace).
Locally, with your changes and mine:

Sweet. Yeah, I was going to say, the only other possibility could be the namespace on the resource ref. Great.