gke-networking

Configures private VPC-native GKE cluster networking with Dataplane V2 and IP planning.

Updated May 11, 2026
One-click install
npx skills add https://github.com/alon3153/upe-social-publisher --skill gke-networking-alon3153
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gke-networking
Source: https://github.com/alon3153/upe-social-publisher/tree/main/.agents/skills/gke-networking
Command: npx skills add https://github.com/alon3153/upe-social-publisher --skill gke-networking-alon3153

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing GKE cluster networking involves many interdependent Day-0 decisions—private nodes, VPC-native IP allocation, DNS endpoints, and Dataplane V2—that cannot be changed after cluster creation. This Skill provides golden-path defaults and configuration guidance so clusters are provisioned with secure, scalable networking from the start. ## Core Features & Use Cases - Golden Path Defaults: Enforces private clusters with private nodes, DNS endpoint access, Dataplane V2, Cloud DNS, and automatic IPAM. - IP Planning Guidance: Provides pod CIDR, service CIDR, and maxPodsPerNode sizing rules to avoid IP exhaustion. - Egress & Access Patterns: Covers Cloud NAT egress, static egress IPs, authorized networks, and bring-your-own VPC/subnet configurations. - Use Case: When provisioning a new GKE Autopilot cluster for a customer with an existing VPC, use this Skill to generate the correct gcloud container clusters create-auto command with secondary ranges, private nodes, and master authorized networks. ## Quick Start Ask the assistant to plan the networking configuration for a new private GKE cluster in a specific region using the golden path defaults.

Frequently Asked Questions about gke-networking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a private GKE cluster with VPC-native networking?▼

Create a private GKE cluster by enabling private nodes, setting the datapath provider to ADVANCED_DATAPATH for Dataplane V2, and enabling automatic IPAM. Use gcloud container clusters create-auto with --enable-private-nodes and --enable-master-authorized-networks flags.

How to access a private GKE cluster from outside the VPC?▼

Access a private GKE cluster externally via its DNS endpoint by setting allowExternalTraffic to true, then running gcloud container clusters get-credentials with the --dns-endpoint flag. No VPN is required for this access pattern.

What pod CIDR size should I use for GKE IP planning?▼

Use a /17 pod CIDR for roughly 32K pod IPs as the golden path default. With maxPodsPerNode set to 48, each node consumes a /25 range; setting it to 110 consumes a /24 per node, reducing how many nodes fit in the CIDR.

Does GKE Dataplane V2 require a separate network policy addon?▼

No, Dataplane V2 provides built-in Network Policy enforcement through eBPF, so no additional addon is needed. Apply default-deny policies per namespace and then allow specific traffic flows.

Can I change the VPC or subnet after GKE cluster creation?▼

No, VPC, subnet, and IP range selections are Day-0 decisions that cannot be changed after cluster creation. Plan secondary ranges for pods and services carefully before provisioning, especially when bringing your own VPC.

When should I not use the gke-networking skill?▼

Do not use it for application ingress, load balancing, or service networking configuration; those belong to the gke-service-networking skill. This skill covers cluster-level networking only, such as private clusters, IPAM, DNS, and egress.