A logistics enterprise is provisioning a private Google Kubernetes Engine (GKE) cluster to host internal microservices. The cluster nodes are created with private IP addresses only, and the cluster control plane is configured with a private endpoint. The platform operations team needs to administer the cluster using kubectl from an on-premises workstation connected to Google Cloud via Cloud VPN. However, connection attempts to the private control plane endpoint are failing. Which configuration change must be made to grant the on-premises workstation access to the private cluster control plane?
- Enable Control Plane Authorized Networks on the GKE cluster and add the on-premises network CIDR range to the allowed IP ranges.Cevap
- BRely on default private cluster peering and avoid configuring Control Plane Authorized Networks, assuming VPC routing automatically opens control plane access to all connected networks.
- CGrant the primitive Owner IAM role (roles/owner) to the platform operations service account to override network firewall rules.
- DGrant the Service Account Admin role (roles/iam.serviceAccountAdmin) on the node service account to the administrative users.
Cevap
Enable Control Plane Authorized Networks on the GKE cluster and add the on-premises network CIDR range to the allowed IP ranges.
Enabling Control Plane Authorized Networks on a private GKE cluster allows administrators to specify exact CIDR blocks—such as on-premises workstation subnets connected via Cloud VPN—that are permitted to reach the private Kubernetes control plane endpoint.
Adım Adım Çözüm
Anahtar Kavram
GKE Private Cluster Control Plane Authorized Networks