kubeadm init Fails Due to "No Space Left on Device" Error on https://labs.play-with-k8s.com/

[FrancescoPaoloL]

Title: kubeadm init Fails Due to "No Space Left on Device" Error

Description:
When running the kubeadm init command on my Kubernetes setup, I encountered multiple errors indicating that there is no space left on the device. The command fails during image pulling and certificate generation phases.

Steps to Reproduce:

Run kubeadm init --apiserver-advertise-address $(hostname -i) on a machine with limited disk space.

Error Log:

vbnet

W0802 06:39:39.690903 485 initconfiguration.go:120] Usage of CRI endpoints without URL scheme is deprecated...
[WARNING SystemVerification]: failed to parse kernel config: unable to load kernel module: "configs"...
[WARNING FileContent--proc-sys-net-bridge-bridge-nf-call-iptables]: /proc/sys/net/bridge/bridge-nf-call-iptables does not exist
[WARNING ImagePull]: failed to pull image registry.k8s.io/kube-controller-manager:v1.27.16: no space left on device
...
error execution phase certs/ca: failure while saving ca certificate and key: couldn't write key: no space left on device

Expected Behavior:
The kubeadm init command should complete successfully without running into disk space issues.

Actual Behavior:
The command fails with multiple "no space left on device" errors during the image pulling and certificate generation phases.

Environment:

Kubernetes Version: v1.27.16
Operating System: Linux
Disk Space Status: Full

Additional Information:
If there are specific configurations or known issues related to disk space that might affect the kubeadm init process, please provide guidance or workarounds.

[a-serr-sentinel]

This is still occurring as of Aug 14th 2024.