Public GKE cluster’s egress traffic via cloud NAT for ip whitelisting

Thank you very much for your answer, this what you comment in point 2 “External NAT gateway: while public Google Kubernetes Engine (GKE) clusters generally use the IPs of the nodes for egress traffic, you can configure a gateway External NAT binding that allows your egress traffic to use a static IP address.This can be achieved by setting up a NAT gateway in the cloud and directing your egress traffic through it.This way regardless of the node you are on the microservice runs, the traffic will exit through the static IP associated with the NAT gateway.” It is what I have configured but it is not working as I expect. Reserved a static ip and created a cloud nat and a cloud router on the same “default” network that created the cluster and assigned the cloud nat the static ip. But when I go inside the microservice and run “curl https://ipinfo.io/ip” I still see the node ip instead of the cloud nat ip, the static one I have associated. Can you think of what I might be missing?