kubernetes: kubectl validation fails when creating a non-v1 object in a v1 list

In other words, you can’t create/replace/delete/apply deployments with kubectl if they’re in a list.

Works as expected:

$ cat nginx-rc.yaml
apiVersion: v1
kind: List
items:
  - apiVersion: v1
    kind: ReplicationController
    metadata:
      name: nginx
    spec:
      replicas: 1
      template:
        metadata:
          labels:
            name: nginx
        spec:
          containers:
            - name: nginx
              image: nginx
$ kubectl create -f nginx-rc.yaml
replicationcontroller "nginx" created

Does not work as expected:

$ cat nginx-dpl.yaml
apiVersion: v1
kind: List
items:
  - apiVersion: extensions/v1beta1
    kind: Deployment
    metadata:
      name: nginx
    spec:
      replicas: 1
      template:
        metadata:
          labels:
            name: nginx
        spec:
          containers:
            - name: nginx
              image: nginx
$ kubectl create -f nginx-dpl.yaml
error validating "nginx-dpl.yaml": error validating data: couldn't find type: v1beta1.Deployment; if you choose to ignore these errors, turn validation off with --validate=false
$ kubectl create -f nginx-dpl.yaml --validate=false
deployment "nginx" created

This is a high priority issue for us, since it means we can’t (easily) use apply (or any kubectl command) with lists of JSON objects since we’ve moved all our replication controllers over to deployment objects, which is hampering the UX of our config efforts.