https://bugzilla.suse.com/show_bug.cgi?id=1214406 Bug ID: 1214406 Summary: [kubeadm1.27] Multiple Issues before `kubeadm init` runs successfully Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: priyanka.saggu@suse.com Reporter: eich@suse.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: Development Blocker: --- 1. The Kubernetes package on TW seems to require cri-o as runtime dependency, however, it requires containerd. Thus, - cri-o should not be installed as a dependency - containerd had to be installed enabled and started (containerd doesn't have an rccontainerd link) 2. kubelet.service does not start: It complains about the option `--container-runtime` not being known. This option is pulled in from /etc/sysconfig/kubelet. It needs to be deleted from this file. It is not clear who has created this file and which package owns it. The rpm database does not know it. Since it is pulled in by ..../systemd/system/kubelet.service.d/10-kubeadm.conf I suspect it comes from kubernetes1.27-kubeadem but it's hard to tell where it is created - at least not in a post-install script. It would be good if the file was '%ghost' in the %files section of the package it originates from. The same is true for the environment file /var/lib/kubelet/kubeadm-flags.env which is written by `kubeadm init`. 3. 'kubeadm init' checks if the kubelet service is enabled. 4. Moreover, it requires a reboot to start all dependent services and load all required kernel modules: - br_netfilter needs to be loaded - containerd needs to be started This was fine for kubic these packages were originally meant for as this had transactional updates and required a reboot. On a 'regular' system where this is not the case, these modules should probably be loaded and services be started from a 'postinstall' script. -- You are receiving this mail because: You are on the CC list for the bug.