cilium: Cilium does not pick up changed node IPs

Bug report

(It may be that this is considered a feature, so feel free to change the label)

General Information

• Cilium version: 1.10.4
• Kernel version: 5.4.0-84-generic
• Orchestration system version in use: Kubernetes 1.21.5

How to reproduce the issue

CiliumNode resources are created with the internalIPs of the Kubernetes node resource at the time that Cilium agent starts. If the internalIPs of the Kubernetes node are then changed, for example due to initialisation by a Cloud Controller Manager, the CiliumNode is not updated. This means that traffic on the pod network does not go over the correct interface.