Closed jayaddison closed 4 years ago
As per details in https://github.com/kubernetes/kubernetes/issues/86094 , the CSINode failures on startup are a symptom of running a v1.16 Kubernetes kubelet against a v1.17 Kubernetes api-server.
CSINode
v1.16
kubelet
v1.17
api-server
The cluster API server has now been upgraded to v1.17 via kubeadm upgrade, and this workaround to disable CSIMigration is no longer required.
kubeadm upgrade
CSIMigration
As per details in https://github.com/kubernetes/kubernetes/issues/86094 , the
CSINodefailures on startup are a symptom of running av1.16Kuberneteskubeletagainst av1.17Kubernetesapi-server.The cluster API server has now been upgraded to
v1.17viakubeadm upgrade, and this workaround to disableCSIMigrationis no longer required.