techiescamp / kubeadm-scripts

Scripts & Kubernetes manifests for Kubeadm Kubernetes cluster setup

• 👋 Hi, I’m @techiescamp

kubeadm-scripts's Issues

The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

i am using public ip for that

[kubelet-check] Initial timeout of 40s passed.

Unfortunately, an error has occurred:
timed out waiting for the condition

This error is likely caused by:
- The kubelet is not running
- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
- 'systemctl status kubelet'
- 'journalctl -xeu kubelet'

Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all running Kubernetes containers by using crictl:
- 'crictl --runtime-endpoint unix:///var/run/crio/crio.sock ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
- 'crictl --runtime-endpoint unix:///var/run/crio/crio.sock logs CONTAINERID'
error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher

Please provide solution how will solve this

keyring needs update in documentation site

getting following errors from current commands:

vagrant@master-node:~$ sudo apt-get update -y
Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease                                                                          
Hit:3 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease                                                                        
Get:4 http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/1.23/xUbuntu_20.04  InRelease [1,626 B]        
Hit:5 http://us.archive.ubuntu.com/ubuntu jammy-security InRelease                                                                         
Get:7 https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_20.04  InRelease [1,642 B]          
Get:6 https://packages.cloud.google.com/apt kubernetes-xenial InRelease [8,993 B]
Err:6 https://packages.cloud.google.com/apt kubernetes-xenial InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B53DC80D13EDEF05
Reading package lists... Done
W: GPG error: https://packages.cloud.google.com/apt kubernetes-xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B53DC80D13EDEF05
E: The repository 'https://apt.kubernetes.io kubernetes-xenial InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

commands causing issue:

sudo curl -fsSL https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo gpg --dearmor -o /etc/apt/keyrings/kubernetes-archive-keyring.gpg

echo "deb [signed-by=/usr/share/keyrings/kubernetes-archive-keyring.gpg] https://apt.kubernetes.io/ kubernetes-xenial main" | sudo tee /etc/apt/sources.list.d/kubernetes.list

new commands that fix issue:

sudo curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key --keyring /usr/share/keyrings/cloud.google.gpg add -

echo "deb [signed-by=/usr/share/keyrings/cloud.google.gpg] https://apt.kubernetes.io/ kubernetes-xenial main" | sudo tee /etc/apt/sources.list.d/kubernetes.list

error with ubuntu version in VagrantFile

Hi,
I encountered an error when trying to run the vagrant file for vm setup. This is the error

master: E: The repository 'http://us.archive.ubuntu.com/ubuntu impish Release' no longer has a Release file.

and the job crashed without continuing with the creation of the nodes

I tried changing the ubuntu version, inserting an older one and everything worked correctly.

My change in vagrant file

from
config.vm.box = "bento/ubuntu-21.10"
to
config.vm.box = "bento/ubuntu-20.04"

everything worked correctly.

Thanks