Like Delete, which can now run over multiple types:
kubectl delete pods,services -l name=foo
Get should be able to span items for label selection
kubectl get pods,services -l name=foo
When a CLI command `kubectl get rc --api-version=v1beta3` is called,
the API resource name should match v1beta3, not whatever the default
RESTMapper version is. This allows the correct resource name to be
returned ("replicationcontrollers", instead of "replicationControllers").
Add a Visitor pattern on top of ResourcesFromArgs
Allows ResourcesFromArgs to return an opaque list of items and have client
commands react to them.
Change request.go to return apiserver errors for arbitrary status codes to
better respond to generic actions that don't make sense (kubectl delete operations foo)
A user who runs `kubectl update -f foo.json` where foo.json is a
resource in a namespace that does not match $(kubectl namespace)
may not intend to update the resource in that other namespace.
For now, return an error when the user does not explicitly set
the namespace via the CLI:
# foo.json in 'one', current is 'two'
$ kubectl update -f foo.json # FAILS
$ kubectl update --namespace=one -f foo.json # SUCCEEDS
* Ensure kubectl uses abstractions from other parts of Kube
* Begin adding abstractions that allow arbitrary objects
* Refactor "update" to more closely match allowed behavior
