ck8s: bootstraping issue of a workload cluster

During the job listed above we can notice the workload cluster failed to be deployed. The first control plane node cannot be bootstraped as the following extract of the console show:

kubectl --context bootstrap -n sylva-system logs libvirt-metal-workload-cp-1-0 -c console-log 
[...]

2025-11-05 22:56:23 ::  [  522.247542] cloud-init[1314]: + echo 'kube-apiserver not yet ready'
2025-11-05 22:56:23 ::  [  522.247622] cloud-init[1314]: kube-apiserver not yet ready
2025-11-05 22:56:23 ::  [  522.248463] cloud-init[1314]: + sleep 1
2025-11-05 22:56:24 ::  [  523.252395] cloud-init[1314]: + k8s kubectl get --raw /readyz
2025-11-05 22:56:24 ::  [  OK  ] Started snap.k8s.k8s-f5862bac-c2e8-46de-b55a-1b5a852a6ce5.scope.
2025-11-05 22:47:53 ::  
2025-11-05 22:47:56 ::  wc-2142490980-ck8s-capm3-virt-workload-cp-1 login:          Mounting snap-snapd-25577.mount - …t unit for snapd, revision 25577...
2025-11-05 22:47:56 ::  [  OK  ] Mounted snap-snapd-25577.mount - Mount unit for snapd, revision 25577.
2025-11-05 22:47:59 ::           Starting snapd.service - Snap Daemon...
2025-11-05 22:48:01 ::  [  OK  ] Started snapd.service - Snap Daemon.
2025-11-05 22:48:02 ::           Mounting snap-k8s-x1.mount - Mount unit for k8s, revision x1...
2025-11-05 22:48:02 ::  [  OK  ] Mounted snap-k8s-x1.mount - Mount unit for k8s, revision x1.
2025-11-05 22:48:03 ::  [  OK  ] Started snap.k8s.hook.install-37b9…-27ec-4965-9870-52eb054f6142.scope.
2025-11-05 22:48:05 ::  [  OK  ] Started snap.k8s.k8sd.service - Service for snap application k8s.k8sd.
2025-11-05 22:48:05 ::  [  OK  ] Started snap.k8s.hook.configure-e4…-c346-4b1f-bdc7-391f30424864.scope.
2025-11-05 22:48:06 ::  [   25.030426] cloud-init[1314]: Warning: flag --classic ignored for strictly confined snap core20
2025-11-05 22:48:06 ::  [   25.030573] cloud-init[1314]: core20 20241206 installed
2025-11-05 22:48:06 ::  [   25.030835] cloud-init[1314]: k8s v1.31.6 installed
2025-11-05 22:48:06 ::  [   25.035033] cloud-init[1314]: + echo 'Snap installation succeeded'
2025-11-05 22:48:06 ::  [   25.035098] cloud-init[1314]: Snap installation succeeded
2025-11-05 22:48:06 ::  [   25.035372] cloud-init[1314]: + return 0
2025-11-05 22:48:06 ::  [   25.035650] cloud-init[1314]: /capi/scripts/disable-host-services.sh
2025-11-05 22:48:06 ::  [   25.035927] cloud-init[1314]: + /capi/scripts/disable-host-services.sh
2025-11-05 22:48:06 ::  [   25.042173] cloud-init[1314]: + for svc in kubelet containerd
2025-11-05 22:48:06 ::  [   25.042258] cloud-init[1314]: + systemctl stop kubelet
2025-11-05 22:48:06 ::  [   25.049154] cloud-init[1314]: Failed to stop kubelet.service: Unit kubelet.service not loaded.
2025-11-05 22:48:06 ::  [   25.051151] cloud-init[1314]: + true
2025-11-05 22:48:06 ::  [   25.051251] cloud-init[1314]: + systemctl disable kubelet
2025-11-05 22:48:06 ::  [   25.058166] cloud-init[1314]: Failed to disable unit: Unit file kubelet.service does not exist.
2025-11-05 22:48:06 ::  [   25.058293] cloud-init[1314]: + true
2025-11-05 22:48:06 ::  [   25.058555] cloud-init[1314]: + for svc in kubelet containerd
2025-11-05 22:48:06 ::  [   25.058832] cloud-init[1314]: + systemctl stop containerd
2025-11-05 22:48:06 ::  [   25.067817] cloud-init[1314]: Failed to stop containerd.service: Unit containerd.service not loaded.
2025-11-05 22:48:06 ::  [   25.067960] cloud-init[1314]: + true
2025-11-05 22:48:06 ::  [   25.068466] cloud-init[1314]: + systemctl disable containerd
2025-11-05 22:48:06 ::  [   25.076070] cloud-init[1314]: Failed to disable unit: Unit file containerd.service does not exist.
2025-11-05 22:48:06 ::  [   25.078073] cloud-init[1314]: + true
2025-11-05 22:48:06 ::  [   25.079345] cloud-init[1314]: /capi/scripts/bootstrap.sh
2025-11-05 22:48:06 ::  [   25.079456] cloud-init[1314]: + /capi/scripts/bootstrap.sh
2025-11-05 22:48:06 ::  [   25.081013] cloud-init[1314]: ++ cat /capi/etc/microcluster-address
2025-11-05 22:48:06 ::  [   25.084157] cloud-init[1314]: + address=:2380
2025-11-05 22:48:06 ::  [   25.084495] cloud-init[1314]: ++ cat /capi/etc/node-name
2025-11-05 22:48:06 ::  [   25.085505] cloud-init[1314]: + name=wc-2142490980-ck8s-capm3-virt-workload-cp-1
2025-11-05 22:48:06 ::  [   25.085880] cloud-init[1314]: + config_file=/capi/etc/config.yaml
2025-11-05 22:48:06 ::  [   25.086405] cloud-init[1314]: + '[' '!' -f /etc/kubernetes/pki/ca.crt ']'
2025-11-05 22:48:06 ::  [   25.086679] cloud-init[1314]: + k8s bootstrap --name wc-2142490980-ck8s-capm3-virt-workload-cp-1 --address :2380 --file /capi/etc/config.yaml
2025-11-05 22:48:06 ::  [  OK  ] Started snap.k8s.k8s-cd3e5e45-dcef-4b0b-9081-769aaf953f54.scope.
2025-11-05 22:48:06 ::  [   25.207917] cloud-init[1314]: Error: Failed to read bootstrap configuration from "/capi/etc/config.yaml".
2025-11-05 22:48:06 ::  [   25.210041] cloud-init[1314]: The error was: failed to parse YAML config file: yaml: unmarshal errors:
2025-11-05 22:48:06 ::  [   25.212079] cloud-init[1314]:   line 112: field etcd-peer-port not found in type apiv1.BootstrapConfig
2025-11-05 22:48:06 ::  [   25.214118] cloud-init[1314]:   line 113: field etcd-port not found in type apiv1.BootstrapConfig
2025-11-05 22:48:06 ::  [   25.216201] cloud-init[1314]: /capi/scripts/load-images.sh
2025-11-05 22:48:06 ::  [   25.217530] cloud-init[1314]: + /capi/scripts/load-images.sh
2025-11-05 22:48:06 ::  [   25.218911] cloud-init[1314]: ++ cat /capi/images/platform
2025-11-05 22:48:06 ::  [   25.220197] cloud-init[1314]: ++ true
2025-11-05 22:48:06 ::  [   25.221082] cloud-init[1314]: + platform=
2025-11-05 22:48:06 ::  [   25.222044] cloud-init[1314]: ++ find /capi/images/ -name '*.tar'
2025-11-05 22:48:06 ::  [   25.223505] cloud-init[1314]: ++ true
2025-11-05 22:48:06 ::  [   25.224374] cloud-init[1314]: ++ sort
2025-11-05 22:48:06 ::  [   25.225257] cloud-init[1314]: /capi/scripts/wait-apiserver-ready.sh
2025-11-05 22:48:06 ::  [   25.226665] cloud-init[1314]: + /capi/scripts/wait-apiserver-ready.sh
2025-11-05 22:48:06 ::  [   25.228111] cloud-init[1314]: + k8s kubectl get --raw /readyz
2025-11-05 22:48:06 ::  [  OK  ] Started snap.k8s.k8s-ee659497-999a-4809-a37b-a5b6c0bcca12.scope.
2025-11-05 22:48:06 ::  [   25.338509] cloud-init[1314]: Error: The node is not part of a Kubernetes cluster. You can bootstrap a new cluster with:
2025-11-05 22:48:06 ::  [   25.340869] cloud-init[1314]:   sudo k8s bootstrap
2025-11-05 22:48:06 ::  [   25.342172] cloud-init[1314]: + echo 'kube-apiserver not yet ready'
2025-11-05 22:48:06 ::  [   25.343586] cloud-init[1314]: kube-apiserver not yet ready
2025-11-05 22:48:06 ::  [   25.344830] cloud-init[1314]: + sleep 1
2025-11-05 22:48:07 ::  [   26.343456] cloud-init[1314]: + k8s kubectl get --raw /readyz
2025-11-05 22:48:07 ::  [  OK  ] Started snap.k8s.k8s-a251f588-2f40-49ea-bf38-fcd051832e8e.scope.
2025-11-05 22:48:07 ::  [   26.449951] cloud-init[1314]: Error: The node is not part of a Kubernetes cluster. You can bootstrap a new cluster with:
2025-11-05 22:48:07 ::  [   26.452313] cloud-init[1314]:   sudo k8s bootstrap
2025-11-05 22:48:07 ::  [   26.453488] cloud-init[1314]: + echo 'kube-apiserver not yet ready'
2025-11-05 22:48:07 ::  [   26.454907] cloud-init[1314]: kube-apiserver not yet ready
2025-11-05 22:48:07 ::  [   26.456165] cloud-init[1314]: + sleep 1
2025-11-05 22:48:08 ::  [   27.454519] cloud-init[1314]: + k8s kubectl get --raw /readyz
Edited by Thomas Monguillon