A cloud administrator provisions a private Google Kubernetes Engine (GKE) cluster for an internal enterprise application. After establishing an active VPN connection to the VPC, the administrator attempts to manage the cluster using `kubectl` from an on-premises management workstation, but connection attempts to the cluster master endpoint time out. Which configuration issue is the cause of this connection failure?
- The control plane authorized networks feature is enabled on the cluster, but the on-premises workstation subnet was omitted from the allowed IP ranges.Answer
- BThe service account attached to the GKE cluster node pool was not granted the primitive Owner role on the Google Cloud project.
- CThe Infrastructure as Code pipeline stored the Terraform state file in an unversioned local directory instead of a Cloud Storage backend.
- DThe project exceeded its regional Compute Engine CPU quota when auto-repairing node instances.
Answer
The control plane authorized networks feature is enabled on the cluster, but the on-premises workstation subnet was omitted from the allowed IP ranges.
In Google Kubernetes Engine (GKE), private clusters allow restricting access to the control plane endpoint via Control Plane Authorized Networks. When this feature is active, traffic from IP addresses outside specified CIDR blocks is blocked by default, causing client connections via `kubectl` to time out even if underlying VPC/VPN routing is functional.
Step-by-Step Solution
Key Concept
GKE Private Cluster Control Plane Authorized Networks