| Kubeadm config file | https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/#config-file |
| How to Setup Kubernetes Cluster on Vagrant VMs | https://devopscube.com/kubernetes-cluster-vagrant/ |
| Setup k8s via kube adm | https://devopscube.com/setup-kubernetes-cluster-kubeadm/ |
POD_CIDR=“10.244.0.0/16”
Installing CRI-O (fixed commands ⇒ https://github.com/cri-o/packaging/blob/main/README.md)
- Install the dependencies for adding repositories
sudo apt-get update
sudo apt-get install -y software-properties-common curl
- Define the Kubernetes version and used CRI-O stream
KUBERNETES_VERSION=v1.29
PROJECT_PATH=prerelease:/main
- Add the Kubernetes repository
curl -fsSL https://pkgs.k8s.io/core:/stable:/$KUBERNETES_VERSION/deb/Release.key |
sudo gpg —dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpg
echo “deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/$KUBERNETES_VERSION/deb/ /” |
sudo tee /etc/apt/sources.list.d/kubernetes.list
- Add the CRI-O repository
curl -fsSL https://pkgs.k8s.io/addons:/cri-o:/$PROJECT_PATH/deb/Release.key |
sudo gpg —dearmor -o /etc/apt/keyrings/cri-o-apt-keyring.gpg
echo “deb [signed-by=/etc/apt/keyrings/cri-o-apt-keyring.gpg] https://pkgs.k8s.io/addons:/cri-o:/$PROJECT_PATH/deb/ /” |
sudo tee /etc/apt/sources.list.d/cri-o.list
- Install the packages
sudo apt-get update
sudo apt-get install -y cri-o
- Start CRI-O
sudo systemctl daemon-reload
sudo systemctl enable crio —now
sudo systemctl start crio.service
Problem : error: error loading config file “/etc/kubernetes/admin.conf”: open /etc/kubernetes/admin.conf: permission denied
SOLUTION :
- Check $KUBECONFIG ⇒ Usually its value is set to /etc/kubernetes/admin.conf
- Then run : unset $KUBECONFIG, so next time kubectl will use .kube/config
Problem :
Found multiple CRI endpoints on the host. Please define which one do you wish to use by setting the ‘criSocketile: unix:///var/run/containerd/containerd.sock, unix:///var/run/crio/crio.sock
To see the stack trace of this error execute with —v=5 or higher
SOLUTION : for cri-o socket add “—cri-socket unix:///var/run/crio/crio.sock”
sudo kubeadm init —apiserver-advertise-address=NODENAME —ignore-preflight-errors Swap —cri-socket unix:///var/run/crio/crio.sock
Problem :
Solution :
sudo mv /etc/kubernetes/pki/ca.crt /etc/kubernetes/pki/ca.crt.backup
Problem : calico assign same ip to 2 pods
Solution : resinstall calico using official instructions https://docs.tigera.io/calico/latest/getting-started/kubernetes/self-managed-onprem/onpremises