fix(concepts): update

Author: RoRoJ

pages/public-gateways/concepts.mdx

@@ -80,6 +80,8 @@ Private Networks attached to legacy Public Gateways must stay in the gateway's a
 When creating a Kubernetes Kapsule cluster with [full isolation](/kubernetes/reference-content/secure-cluster-with-private-network/#can-i-use-a-public-gateway-with-my-private-network-to-exit-all-outgoing-traffic-from-the-nodes) you are required to attach a Public Gateway to the cluster's Private Network, and this **cannot** be a legacy Public Gateway - it must be an IPAM-mode gateway.
 </Message>
 
+See also our dedicated documentation on [moving Public Gateways to IPAM-mode](/public-gateways/reference-content/understanding-v2/) to ensure compatibility with our new API v2.
+
 ## Legacy gateway
 
 See [IPAM](#ipam).