Agent skill · software engineering · google
gke-service-networking
Configures GKE edge networking, traffic routing, load balancing, and private service endpoints. Use when configuring Gateway API manifests, standard Ingress, Cloud Armor WAF security policies, Container-Native Load Balancing (NEGs), Private Service Connect (PSC), or Google-managed SSL certificates on GKE, and to troubleshoot Ingress and load-balancer 502/5xx errors, backend health-check failures, connection draining, and TLS/SSL policy enforcement. Don't use for core cluster IP planning, Dataplane V2 network policies, or node NAT egress (use gke-networking instead).
Why this skill is useful
Provides specific GKE networking configurations and manifests that the AI wouldn't reliably generate on its own.
What it needs
About 6k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.
What this skill does
GKE Service Networking Skill This skill provides workflows for exposing applications running on GKE securely to the internet or internal networks. Deployable manifest templates live in assets/ — edit the # Replace ... placeholders before applying. Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read Usage Attribution. For commands executed directly in the terminal (never in generated scripts, Terraform, or user code), prefix gcloud with CLOUDSDKMETRICSREQUESTATTRIBUTION="agent-skills/1.0 (skill:gke-service-networking)" and append agent-skills/1.0 (skill:gke-service-networking) to User-Agent headers. Workflows 1. Configure Gateway API (Recommended) The Gateway API is the modern way to manage routing in Kubernetes. Prerequisites: Gateway API must be enabled on the cluster (enabled by default on new clusters running GKE 1.26+; on older supported versions enable it with --gateway-api=standard). Templates: assets/gateway.yaml — external Gateway using the gke-l7-global-external-managed GatewayClass with an HTTP listener. assets/httproute.yaml — HTTPRoute attaching to the Gateway via parentRefs and routing a path prefix to a Service backendRef. assets/httproute-traffic-split.yaml — HTTPRoute demonstrating weighted traffic splitting (e.g. 90/10) for canary deployments across backend services. Traffic Splitting (Canary Deployments): HTTPRoute supports weighted traffic splitting across multiple backend Services for canary rollouts: 2. Configure Standard GKE Ingress Use standard Ingress for simpler use cases or legacy setups. Template: assets/ingress.yaml — GCE Ingress (kubernetes.io/ingress.class: "gce" annotation) routing to a Service. 3. Secure with Cloud Armor Cloud Armor provides WAF and DDoS protection. 1. Create a Security Policy in Cloud Armor: 2. Reference it in a BackendConfig: assets/backendconfig.yaml (sets spec.securityPolicy.name). 3. Associate the BackendConfig with your Service via annotations: 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/gke-service-networking