How I run CRI rktlet remote during development

example.sh

terminal-1 rktlet-repo $ make
terminal-1 rktlet-repo $ sudo ./bin/rktlet -logtostderr -v=10

------

terminal-2 k8s-repo $ cat env.rktlet
export ENABLE_NODE_LOGGING=false
export ENABLE_CLUSTER_MONITORING=none
export KUBELET_HOST=0.0.0.0

export CGROUPS_PER_QOS=false # TODO
export CGROUP_DRIVER=systemd # TODO this doesn't work
export LOG_LEVEL=4 # To taste
export CONTAINER_RUNTIME=remote
export IMAGE_SERVICE_ENDPOINT=/var/run/rktlet.sock
export CONTAINER_RUNTIME_ENDPOINT=/var/run/rktlet.sock

export NET_PLUGIN="" # TODO
export ALLOW_SECURITY_CONTEXT=yes
export ALLOW_PRIVILEGED=yes

terminal-2 k8s-repo $ source ./env.rktlet
terminal-2 k8s-repo $ ./hack/local-up-cluster.sh

------

terminal-3 k8s-repo $ # wait for previous command to be done
terminal-3 k8s-repo $ # Run the commands it prints out (cluster/kubectl.sh config ....)
terminal-3 k8s-repo $ ./cluster/kubectl describe nodes #validate rkt printed as runtime with v0.1.0

env.rktlet is missing a export EXPERIMENTAL_CRI=true?