You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When changing the talos version in the TalosControlPlane, a new node talos-swo-wym is brought up from a spare server, and takes over the kube-vip address from the old owner/node talos-96c-ge9. The old node talos-96c-ge9 is being removed from the cluster, and once connectivity is back up, the old node errors because it can't find itself as a node in the cluster anymore.
Manual intervention is required to reboot the server, so it will be put back in to the unallocated pool of spare servers.
The text was updated successfully, but these errors were encountered:
When changing the talos version in the TalosControlPlane, a new node
talos-swo-wym
is brought up from a spare server, and takes over the kube-vip address from the old owner/nodetalos-96c-ge9
. The old nodetalos-96c-ge9
is being removed from the cluster, and once connectivity is back up, the old node errors because it can't find itself as a node in the cluster anymore.Manual intervention is required to reboot the server, so it will be put back in to the unallocated pool of spare servers.
The text was updated successfully, but these errors were encountered: