kubevirt: virtctl not working, configuration location not documented in how to guide

Is this a BUG REPORT or FEATURE REQUEST?: BUG Uncomment only one, leave it on its own line: /kind bug

What happened: Followed the install guide, was able to successfully install and start a vm, but only using the kubectl apply and patch commands. The virtctl tool does not work regardless of whether i install with crew or just use the amd linux command line tool.

What you expected to happen: kubectl virt version should return the server version from the kubevirt ns (I tried having default k8s context be kubevirt and default with no luck)

# Start the virtual machine:
kubectl patch virtualmachine myvm --type merge -p \
    '{"spec":{"running":true}}'

./virtctl stop testvm
Error stopping VirtualMachine the server could not find the requested resource

How to reproduce it (as minimally and precisely as possible): Follow the create your kubevirt vm guide found here

Anything else we need to know?: I also tried to change the service of the server/api to a NodePort. That also failed, I am not sure how or where configuration for kubevirt cli is normally set.

NAME                                   READY   STATUS    RESTARTS   AGE
pod/virt-api-788f97c65b-qrt4l          1/1     Running   0          68m
pod/virt-api-788f97c65b-wt8bb          1/1     Running   0          68m
pod/virt-controller-6f6695b47c-nphml   1/1     Running   0          67m
pod/virt-controller-6f6695b47c-r59t9   1/1     Running   0          67m
pod/virt-handler-7dhvs                 1/1     Running   0          67m
pod/virt-handler-vm9cd                 1/1     Running   0          67m
pod/virt-handler-x9gsq                 1/1     Running   0          67m
pod/virt-launcher-testvm-qpkcl         2/2     Running   0          46m
pod/virt-operator-688dddf777-492zc     1/1     Running   0          69m
pod/virt-operator-688dddf777-z5sl2     1/1     Running   0          69m

NAME                                  TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)         AGE
service/kubevirt-prometheus-metrics   ClusterIP   10.43.147.227   <none>        443/TCP         68m
service/virt-api                      NodePort    10.43.168.200   <none>        443:32179/TCP   68m

NAME                          DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
daemonset.apps/virt-handler   3         3         3       3            3           <none>          67m

NAME                              READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/virt-api          2/2     2            2           68m
deployment.apps/virt-controller   2/2     2            2           67m
deployment.apps/virt-operator     2/2     2            2           69m

NAME                                         DESIRED   CURRENT   READY   AGE
replicaset.apps/virt-api-788f97c65b          2         2         2       68m
replicaset.apps/virt-controller-6f6695b47c   2         2         2       67m
replicaset.apps/virt-operator-688dddf777     2         2         2       69m

NAME                            AGE   PHASE
kubevirt.kubevirt.io/kubevirt   1h    Deployed

NAME                                        AGE   PHASE     IP           NODENAME
virtualmachineinstance.kubevirt.io/testvm   46m   Running   10.42.2.19   ip-omitted

NAME                                AGE   RUNNING   VOLUME
virtualmachine.kubevirt.io/testvm   48m   true

Environment:

• KubeVirt version (use virtctl version): “v0.20.1”
• Kubernetes version (use kubectl version): “v1.13.4”
• VM or VMI specifications: The test vm
• Cloud provider or hardware configuration: Hardware / Rancher Cluster
• OS (e.g. from /etc/os-release): CentOS 7.5+
• Kernel (e.g. uname -a): N/A
• Install tools: https://kubevirt.io/user-guide/docs/latest/administration/intro.html
• Others: