QuestionQ112

VerifiedEnsuring the successful operation of a cloud solution

You are deploying an application to Google Kubernetes Engine (GKE) that needs to call an external third-party API. You need to provide the external API vendor with a list of IP addresses for their firewall to allow traffic from your application. You want to follow Google-recommended practices and avoid any risk of interrupting traffic to the API due to IP address changes. What should you do?

Explanation

Cloud NAT with static IP addresses provides consistent, predictable egress IP addresses for all traffic originating from the GKE cluster. This allows you to provision a fixed allowlist with the third-party API provider without risk of IP changes during cluster scaling. With dynamic (automatic) NAT IP allocation, Cloud NAT adds and removes addresses as needed and you cannot predict the next address, so manual assignment of static IP addresses is the documented choice when a destination relies on an allowlist. Private GKE nodes combined with Cloud NAT is the recommended approach for outbound firewall integration.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!