Rapid News Brief

Google listed GKE Granular NAT in Preview Nov. 18, giving teams namespace-level control over outbound source IP addresses. The feature supports Autopilot and Standard clusters running version 1.37.1-gke.2611000 or later with GKE Dataplane V2 enabled. It uses CloudNATGateway and TrafficSelector custom resources rather than applying one NAT policy to the entire cluster.

The release distinguishes dedicated external IP addresses for Public NAT from dedicated subnet address ranges for Private NAT. Teams can route selected namespaces through those addresses without custom proxy instances, Google says.

Enabling it can disrupt workloads

The configuration guide includes a significant migration warning: enabling Granular NAT on an existing cluster during Preview recreates every node pool and can disrupt running workloads. Selection is limited to namespaces. The preview cannot select individual Pods or Service Accounts through label selectors within a namespace.

The same guide describes two configuration objects. CloudNATGateway provisions a gateway or connects to an existing one in the cluster’s region and VPC network. TrafficSelector maps source namespaces and destination address ranges to that gateway. Those are routing choices that require an application inventory, not simply a new feature toggle.

The namespace is the boundary

Kubernetes’ namespace guide describes namespaces as a way to group resources within one cluster. Resource names must be unique inside a namespace, not across all namespaces. Namespace scoping does not cover cluster-wide objects such as nodes or persistent volumes. Namespaces cannot be nested; a namespaced resource belongs to only one. The project distinguishes that organizational scope from labels used to separate slightly different resources inside a namespace.

For operators, the practical question is which application groups need predictable source addresses and how those groups align with existing namespaces. Review that mapping before planning enablement on a running cluster. The release creates a new routing option; it does not establish that a particular migration will be nondisruptive or that an external partner’s access requirements have been met.