Issue with Grub update & kubeadm CA cert verification

[thomasriley]

Hey,

Thanks for putting this together.

Just been using this to learn some K8 stuff and I come across a few issues with the mater.sh & node.sh scripts.

Firstly, when the script runs an apt-get update to update the system it hangs on the below in the cloud-init-output.log:

A new version of /boot/grub/menu.lst is available, but the version installed
currently has been locally modified.

  1. install the package maintainer's version
  2. keep the local version currently installed
  3. show the differences between the versions
  4. show a side-by-side difference between the versions
  5. show a 3-way difference between available versions
  6. do a 3-way merge between available versions (experimental)
  7. start a new shell to examine the situation

What would you like to do about menu.lst?

I'm more familiar with RHEL but a quick bit of research reveals that setting DEBIAN_FRONTEND=noninteractive will ensure Debian selects the default in this scenario. I added this to my master.sh & node.sh scripts locally and it resolved this issue.

Secondly, bootstrapping the nodes using the node.sh script results in this error:

[preflight] Running pre-flight checks.
        [WARNING FileExisting-crictl]: crictl not found in system path
discovery: Invalid value: "": using token-based discovery without DiscoveryTokenCACertHashes can be unsafe. set --discovery-token-unsafe-skip-ca-verification to co
ntinue

As described in the error, adding --discovery-token-unsafe-skip-ca-verification to co ntinue to the kubeadm command resolves this.

I will raise a pull request with these fixes.