WARNING FileExisting-crictl]: crictl not found in system path
Qambar opened this issue · 3 comments
During the terraform apply command when it starts the kubeadm with master-configuration.yml. We can see in the logs following warning about missing crictl in system path
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [init] Using Kubernetes version: v1.9.0
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [init] Using Authorization modes: [Node RBAC]
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [preflight] Running pre-flight checks.
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [WARNING FileExisting-crictl]: crictl not found in system path
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [certificates] Generated ca certificate and key.
According to kubernetes1-9-0-kubeadm-init-crictl-not-found-in-system-path on stackoverflow. We need to install the crictl which has a dependency on golang.
This is currently not a part of provisioning.
Related: https://github.com/kubernetes/kubeadm/blob/master/docs/design/design_v1.9.md#preflight-checks
If I understand this correctly, the warning can be safely ignored.
Indeed, i was able to by pass that warning and it didn't complain about it any further.
I think we can simply ignore this for the time being. There's also a proposal to automatically install this dependency if it's not available. See: kubernetes/kubeadm#613