Kubespy only says "Server is unable to handle /v1, Kind=pod"

[mabushey]

$ kubectl get all -n container-stg                                                                                                                                              

NAME                              READY     STATUS    RESTARTS   AGE
pod/container-847fbf5549-p7djz   2/2       Running   1          1h
pod/container-847fbf5549-w2mpc   2/2       Running   1          1h
pod/container-847fbf5549-zcmtp   2/2       Running   1          1h

NAME                         TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
service/container-service   ClusterIP   100.71.215.197   <none>        4000/TCP   1h
NAME                         DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/container   3         3         3            3           1h

NAME                                    DESIRED   CURRENT   READY     AGE
replicaset.apps/container-847fbf5549   3         3         3         1h

kubespy status v1 pod container
2018/09/24 23:39:38 Server is unable to handle /v1, Kind=pod
kubespy status apps/v1 pod container
2018/09/24 23:39:43 Server is unable to handle apps/v1, Kind=pod

1. I have no clue the purpose of the 2nd argument. Is there any way of specifying a wildcard or having kubespy figure it out?
2. How do you make it view the status of a pod?

[hausdorff]

1. v1 and Pod are the apiVersion and kind of the object you'd like to observe the status of. There are many resource types in Kubernetes, each of which is uniquely identified by a combination of these two things. Because users can choose to observe the status of both any resource type, we need both of these to be specified to start observing -- we can't really do a "wildcard" thing here.
2. Pod currently must be capitalized right now. In the future we might allow aliases or something. At the very least we might want to make this caps-insensitive.

[hausdorff]

Also, apps/v1 is not a valid apiVersion for Pod. It must be v1. :)

[mabushey]

Thanks!!

[hausdorff]

I'll keep this open too so I can remember to make the experience more friendly.

[hausdorff]

Ok, I believe #21 has rounded off the major edge on this (the capitalization issue). The rest of these issues should be resolved in the upcoming usability sweep, I think.