Add kube-proxy clusterCIDR note to migrate pools documentation

Co-authored-by: caseydavenport <1944093+caseydavenport@users.noreply.github.com>

Author: Copilot

calico-cloud/networking/ipam/migrate-pools.mdx

@@ -48,6 +48,8 @@ If you follow these steps, existing pod connectivity will not be affected. (If y
 
    It is highly recommended that your Calico IP pools are within the Kubernetes cluster CIDR. If pods IPs are allocated from outside of the Kubernetes cluster CIDR, some traffic flows may have NAT applied unnecessarily causing unexpected behavior.
 
+   Additionally, if your cluster uses the `--cluster-cidr` argument with kube-proxy, ensure that the cluster CIDR includes the new IP pool CIDR. Some clusters may not specify a cluster CIDR, and others may already have a cluster CIDR that encompasses the new pool, in which case no kube-proxy configuration change is needed.
+
    :::
 
 1. Disable the old IP pool.

calico-enterprise/networking/ipam/migrate-pools.mdx

@@ -50,6 +50,8 @@ If you follow these steps, existing pod connectivity will not be affected. (If y
 
    It is highly recommended that your Calico IP pools are within the Kubernetes cluster CIDR. If pods IPs are allocated from outside of the Kubernetes cluster CIDR, some traffic flows may have NAT applied unnecessarily causing unexpected behavior.
 
+   Additionally, if your cluster uses the `--cluster-cidr` argument with kube-proxy, ensure that the cluster CIDR includes the new IP pool CIDR. Some clusters may not specify a cluster CIDR, and others may already have a cluster CIDR that encompasses the new pool, in which case no kube-proxy configuration change is needed.
+
    :::
 
 1. Disable the old IP pool.

calico/networking/ipam/migrate-pools.mdx

@@ -50,6 +50,8 @@ If you follow these steps, existing pod connectivity will not be affected. (If y
 
    It is highly recommended that your Calico IP pools are within the Kubernetes cluster CIDR. If pods IPs are allocated from outside of the Kubernetes cluster CIDR, some traffic flows may have NAT applied unnecessarily causing unexpected behavior.
 
+   Additionally, if your cluster uses the `--cluster-cidr` argument with kube-proxy, ensure that the cluster CIDR includes the new IP pool CIDR. Some clusters may not specify a cluster CIDR, and others may already have a cluster CIDR that encompasses the new pool, in which case no kube-proxy configuration change is needed.
+
    :::
 
 1. Disable the old IP pool.