https://bugzilla.suse.com/show_bug.cgi?id=1214406 https://bugzilla.suse.com/show_bug.cgi?id=1214406#c8 --- Comment #8 from Priyanka Saggu <priyanka.saggu@suse.com> --- Hey Egbert, I've raised the following SRs: - cri-o ~ https://build.opensuse.org/request/show/1108439 - kubernetes1.27 ~ https://build.opensuse.org/request/show/1108445 - containerd ~ https://build.opensuse.org/request/show/1108423 With these changes, I was able to have a successful `kubeadm init` run! # Although - before `kubeadm init`, I had to manually load the kernel modules (doing that in %post scriptlet didn't work, it complained for modprobe not found. Nor did adding it as `ExecStartPre=` in 10-kubeadm.conf work. I'll explore more options)
sudo modprobe overlay && sudo modprobe br_netfilter
# with cri-o as CRI sudo kubeadm init --kubernetes-version 1.27.4 --cri-socket=unix:///var/run/crio/crio.sock
# with containerd as CRI sudo kubeadm init --kubernetes-version 1.27.4 --cri-socket=unix:///var/run/containerd/containerd.sock
---
3. It seems like cri-o is released in tandem with kubernetes (the versions are in sync). Therefore, 1. cri-o should be updated in tandem with kubernetes. 2. Dependencies between cri-o and kubernetes should be set so that only matching versions are installed.
I agree ^. I'll fix the crio/kubernetes version dependency part. -- You are receiving this mail because: You are on the CC list for the bug.