Max Gautier fcecaf6943

wait for control plane node to become ready after joining (#12794) ...

When joining a control plane node and "upgrading" the cluster setup (for
example, to update etcd addresses after adding a new etcd) in the same
playbook run, the node can take a bit of time to become ready after
joining.
This triggers a kubeadm preflight check (ControlPlaneNodesReady) in
kubeadm upgrade, which is run directly after the join tasks.

Add a configurable wait for the control plane node to become Ready to
fix this race condition.

2026-01-28 22:15:51 +05:30

..

client

refact ip stack (#11953)

2025-02-11 03:37:58 -08:00

control-plane

wait for control plane node to become ready after joining (#12794)

2026-01-28 22:15:51 +05:30

kubeadm

Fix breakage when ignoring all kubeadm preflight errors (#12606)

2025-10-13 05:54:58 -07:00

kubeadm_common

Stricter kubeadm validation (config and runtime checks) (#11710)

2024-11-15 06:34:52 +00:00

node

fix syntax in haproxy.cfg.j2 for IPv6 binding (#12862)

2026-01-14 12:33:35 +05:30

node-label/tasks

Do not use ‘yes/no’ for boolean values (#11472)

2024-08-28 06:30:56 +01:00

node-taint/tasks

fix(kubernetes): taint nodes with kubectl (#10705)

2024-01-23 15:46:13 +01:00

preinstall

Fix: ansible_facts.selinux.status added. (#12861)

2026-01-14 23:31:40 +05:30