On GCP Cloud, we have noticed an interesting behavior: after a node goes through the eviction process, its IP addresses change. Some resource values on a node are immutable, meaning they can't be changed or fixed after a reboot. Examples of these immutable values include PodCIDRs, or the CNI caches.
Probably the best way to solve this issue is to delete the node resource during the shutdown process. This way, after the node reboots, it can rejoin the cluster, and the CCM can properly initialize the node again.
Feature Request
Description
On GCP Cloud, we have noticed an interesting behavior: after a node goes through the eviction process, its IP addresses change. Some resource values on a node are immutable, meaning they can't be changed or fixed after a reboot. Examples of these immutable values include PodCIDRs, or the CNI caches.
Probably the best way to solve this issue is to delete the node resource during the shutdown process. This way, after the node reboots, it can rejoin the cluster, and the CCM can properly initialize the node again.