grunlab

Thank you SteeMan, Igor
New image Armbian_23.02.3_Odroidxu4_bullseye_current_5.4.239_minimal.img.xz is now working perfectly.

FYI:
 
- I've reinstalled one of the cluster node using the last image Armbian_20.02.1_Odroidxu4_buster_current_5.4.19_minimal.img:
 
adrien@bastion:~ $ kc get node worker-03 -o wide
NAME        STATUS   ROLES    AGE   VERSION   INTERNAL-IP     EXTERNAL-IP   OS-IMAGE                       KERNEL-VERSION     CONTAINER-RUNTIME
worker-03   Ready    <none>   11m   v1.17.3   192.168.0.106   <none>        Debian GNU/Linux 10 (buster)   5.4.19-odroidxu4   docker://19.3.8
 
- pids cgroup is enabled on this image:
 
adrien@worker-03:~$ cat /proc/cgroups | grep pids
pids    3    97
 
- No more warning at kubernetes logs level and the node looks stable for the moment :-)
 
I think this topic can be closed now.

ok, ok ... no problem :-)
I'm living without this kernel feature for a while and i didn't notice real impact at k8s level except those warning in the logs ...
 
I will try to investigate on my side ...

My Ubuntu VM is no longer booting to X since the last apt upgrade which makes preparing updates slightly more annoying than it should be, but I can have a go at rebuilding the kernel this evening.