Diagram
Workstation kubectl reaches the control-plane kube-apiserver on TCP 443 via two paths: recommended Connect gateway through Google and gke-connect-agent, or direct private ELB endpoint inside the VPC.
Connection Paths to the Control Plane
The connection path determines how traffic flows from kubectl to the cluster control plane. The recommended path is the Connect gateway, a Google-hosted reverse proxy where the gke-connect-agent Deployment in the cluster carries requests between Google and the control plane. The alternative path is a private endpoint, where kubectl sends requests directly to the private DNS name of the control plane inside the cloud virtual network. The two options differ in traffic flow and network requirements:
| Connection option | How kubectl traffic flows | Network requirement |
|---|---|---|
| Connect gateway | Traffic flows from kubectl to connectgateway.googleapis.com to the private endpoint through the agent | Cluster needs outbound connectivity to Google; no direct VPC route to the control plane is required |
| Private endpoint | Traffic flows from kubectl directly to the private control-plane endpoint, such as an ELB DNS name on AWS | Workstation needs routing to the control-plane endpoint in the AWS Virtual Private Cloud or Azure Virtual Network, and firewall rules may need to be widened |
Domain 8 of 11
24 practice questions
Practice this DomainLast updated