Description of problem:
Certain resources will return that they have a label present when they do not. 

# notice how the componentstatus resources claim to have cr_applied label
[ec2-user us-east-1 ~]$ oc get ComponentStatus -l cr_applied
NAME                 STATUS    MESSAGE             ERROR
controller-manager   Healthy   ok                  
scheduler            Healthy   ok                  
etcd-1               Healthy   {"health":"true"}   
etcd-2               Healthy   {"health":"true"}   
etcd-0               Healthy   {"health":"true"}   

# But do not
[ec2-user us-east-1 ~]$ oc get ComponentStatus scheduler -o=yaml
apiVersion: v1
conditions:
- message: ok
  status: "True"
  type: Healthy
kind: ComponentStatus
metadata:
  creationTimestamp: null
  name: scheduler
  selfLink: /api/v1/componentstatuses/scheduler

# Most resources are correctly filtered
[ec2-user us-east-1 ~]$ oc get all -l cr_applied
No resources found.





Version-Release number of selected component (if applicable):
version   4.0.0-0.alpha-2019-02-24-225217

How reproducible:
100%

Steps to Reproduce:
1. oc get componentstatus -l anylabel
2. 
3.

Actual results:
Componentstatuses are returned though they do not possess the label


Expected results:
Only resources with the label, regardless of kind, should be returned

Additional info: