Closed CraigSterrett closed 4 years ago
Looks like it's not a Clear or cloud native stack issues.
On CentOS [root@okd-master centos]# kubeadm init --config=./kubeadm.yaml W0114 00:07:01.739102 30267 validation.go:28] Cannot validate kube-proxy config - no validator is available W0114 00:07:01.739199 30267 validation.go:28] Cannot validate kubelet config - no validator is available
I guess it's covered by this https://github.com/kubernetes/kubeadm/issues/1913
Running kubeadm displays warnings, not sure if this is specific to Clear or a bug in kubeadm for 1.17
W0111 00:13:01.708910 29892 validation.go:28] Cannot validate kubelet config - no validator is available W0111 00:13:01.708952 29892 validation.go:28] Cannot validate kube-proxy config - no validator is available