I'm running crio 1.17.0-rc1 with kubernetes 1.17.1 on RHEL7/CENTOS7. One thing I had to do was build crio 1.17 myself because there was no package available and I read the version should match (crio 1.17 and k8 1.17).
I am using systemd as the cgroup driver. I'm not sure what your issue might be, but my setup goes like this:
Going from this, your ClusterRole isn't configured to allow access to deployments, and the ClusterRole you've listed isn't properly bound to your service account. You could configure it with something like I did below as a troubleshooting measure/to make sure you're able to properly configure permissions and rule out an issue with the serviceaccount's role ...
Possibly you are looking for this feature which is closed with no action since there are ways to work around this problem.
kubeadm already allows to set taints for the joining node using the configuration file at join time (check my other answer for details on how to do that)
One Other way to achieve this is by running join as usual but taking few extra ...
Environment vars at the time of kubeadm init are not deployed to all pods. There are no pods at that time anyway, you have just created a kubemaster.
When you want to put NO_PROXY into pods/deployments you have to do that the usual way with env on the container.
- name: NODE_NAME
In kubeadm docs
--cri-socket stringPath to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket.