OCSK: After Running 'kubeadm-ha-setup up/join' the '/var/lib/kubelet' Filesystem is Umounted (Doc ID 2542743.1)

Last updated on SEPTEMBER 23, 2022

Applies to:

Symptoms

Before calling kubeadm-ha-setup up/join all kubernetes cluster nodes have /var/lib/kubelet mounted as below, in a dedicated filesystem.

#df /var/lib/kubelet
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdb3 20511312 45080 19401272 1% /var/lib/kubelet

But after running kubeadm-ha-setup up/join the /var/lib/kubelet is unmounted and the root partition is used instead,

#df /var/lib/kubelet
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda2 20005712 3572328 15394076 19% /

If any of the kubernetes nodes are being rebooted the kubelet service will not restart because it will complain about missing /var/lib/kubelet/config.yaml
The config.yaml will be missing because the rebooting re-mounts /var/lib/kubelet and the empty partition "covers up" the files on the root partition.

Changes

Installing High Availability Oracle Container Services for use with Kubernetes cluster with kubeadm-1.12.7-1.1.2.el7.X86_64

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.