Caught on t122 (7e519eb997af236c, 2026-05-16): primary + sin patched
fine, but nbg1's kubectl patch failed because the Node object hadn't
yet appeared in the apiserver between healthz OK and Node registration.
Result: nbg1 stuck at providerID=k3s://... → CCM rejected its LB
allocation → clustermesh-apiserver external_ip stayed <pending> on
nbg1 → AutoEstablishClusterMesh couldn't fully mesh.
Add a 30-iter loop (150s budget): get node first; if found, patch; else
sleep 5. Hetzner apiserver registers Nodes within ~10-30s of k3s
install on healthy clusters.
Co-authored-by: claude <claude@anthropic.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0ebd137547