-
Notifications
You must be signed in to change notification settings - Fork 107
list/watch resources across all namespaces #32
Conversation
@ultimateboy I was thinking about this recently and I don't know if I like the current behavior for Lists. E.g. that this
Defaults to the client's "default" namespace. It's not very explicit. Maybe we could make the
So you can do
That would prevent adding more methods and clean up the ambiguous of
What do you think? |
I'd be ok with this. I was actually kinda surprised that passing an empty string meant the pod's namespace instead of all-namespaces. I implemented it this way because it's what was in the original issue and I did not want to break backwards compatibility. |
@ericchiang Let me know if you want me to go ahead and update this PR with the proposed new direction. I would ask that you make a new release before we implement breaking changes. |
@ultimateboy yep, go ahead and update. I'll create a release once you're done and call out the change. |
cb6c841
to
4f04aff
Compare
@ericchiang ready for review |
@ultimateboy awesome! could you add a test? (also can you run the tests? I've only ever tried on my machine) https://github.com/ericchiang/k8s/blob/master/client_test.go |
Changes previous default behavior where an empty string namespace would use the client's namespace instead of all-namespaces. Now, an emtpy string equates to all-namespaces (there is a k8s.AllNamespaces constant as well).
4f04aff
to
44d7780
Compare
@ericchiang Test has been added.
|
lgtm! |
Fixes #21