
A private GKE cluster can disable its public control plane endpoint, which leaves the private endpoint as the only way for kubectl to reach the control plane. Who can reach that endpoint is then decided by control plane authorized networks, and for older private clusters, by VPC Network Peering routes as well. For the Professional Cloud Network Engineer exam, the useful skill is telling an authorized networks question apart from a routing question when control plane access fails.
Control plane authorized networks limit which source ranges can reach the control plane endpoint, and a cluster can enforce authorized networks on the private endpoint as well as the public one. The primary range of the node subnet is allowed automatically. That is why nodes and workloads keep running normally even when the authorized networks list is short.
Every other source range has to be listed explicitly, including other subnets in the same VPC network. The control plane itself enforces the list and drops requests from ranges that are not on it, so the authorized networks list is where control plane access is granted. The private endpoint is reached inside Google's network, through VPC Network Peering or Private Service Connect.
Older private clusters add a routing constraint on top of authorized networks. Their control plane lives in a Google-managed VPC network that is peered to the cluster's network. VPC Network Peering is not transitive, so a third network peered with the cluster's network has no route to the control plane. Authorized networks decide which sources the control plane accepts, but they cannot create a route, so a source needs a path to the control plane before its entry on the list matters.
One pattern that works within the non-transitive rule while keeping traffic on internal addresses is a proxy on a VM in the cluster's node subnet:
Each hop crosses only one peering, which is what the non-transitive rule requires.
Two flags are easy to conflate when reading cluster creation commands:
--enable-private-nodes keeps nodes on internal addresses only.--enable-master-authorized-networks only limits which sources can reach the control plane.Private nodes are about node addressing, and authorized networks are about access to the control plane. A Professional Cloud Network Engineer exam requirement about one does not get satisfied by the other, so we would match each requirement to the flag that controls it.
Our Professional Cloud Network Engineer practice exams cover GKE private clusters alongside GKE IP address planning and VPC Network Peering, with detailed explanations that drill these distinctions.