LFS258 Lab 3.1 #14

Hi @cziaul,

You would receive the "command not found" message when the Kubernetes components, kubeadm, kubelet, and kubectl, have not been successfully installed.
I'd recommend revisiting steps 5, 6, 7, and 8.
After executing step 5, run cat /etc/apt/sources.list.d/kubernetes.listand compare the output with the lab exercise.
For step 6, running the command as a single-liner may help, because some CLI tools do not play nicely with multi-line commands: curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -
After the first command in step 8, where you install the Kubernetes components, verify with which kubeadm to make sure it was installed. If the install was successful it will output the path where the binary has been installed on the system. No response of any kind means that it did not get installed.

Regards,
-Chris

@cziaul Responses can take up to 2 business days (no weekends or holidays included), therefore we appreciate your understanding and patience.

Hi @cziaul,

Thanks for the detailed info provided. To resolve the cri-socket conflict, you can supply the additional flag on step 4.x as: --cri-socket= /var/run/crio/crio.sock

One concerning aspect of your Kubernetes nodes setup is the IP addresses of your nodes overlapping the Pod network IP range 192.168.0.0/16 supplied and managed by Calico. This is encountered often when working with VirtualBox and will lead to DNS issues in later lab exercises. With Kubernetes, you would want to have separate/non-overlapping networks for cluster nodes and the Pods.

Regards,
-Chris

Great! As Chris said often this issue is due to overlap or other host-based issue. Glad its working with GCE.