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
We are using GCP and I tried to test the configuration of kube IP by restarting a node and see if the static IP was correctly restored. The kube IP daemon does not start a new pod (that one that was previously deleted with the node stop) for the restarted node.
The issue is that, once restarted, a node loses its custom label (kubeip.com/public=true).
It sounds like a bug, but I could not find any solution to that.
I would be curious to know how others implemented it.
The text was updated successfully, but these errors were encountered:
We are using GCP and I tried to test the configuration of kube IP by restarting a node and see if the static IP was correctly restored. The kube IP daemon does not start a new pod (that one that was previously deleted with the node stop) for the restarted node.
The issue is that, once restarted, a node loses its custom label (
kubeip.com/public=true).It sounds like a bug, but I could not find any solution to that.
I would be curious to know how others implemented it.
The text was updated successfully, but these errors were encountered: