Gke Service Networking
GoogleOfficialPublished by Google
- Skill
- Tool integration
- Cloud and DevOps
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides structured workflows for managing GKE edge networking, including Gateway API, standard Ingress, Cloud Armor security, and Container-Native Load Balancing. It assists in configuring traffic routing, SSL certificates, and Private Service Connect, while offering troubleshooting guidance for common load-balancer errors like 502/5xx responses and health-check failures.
What it does
- Configures Gateway API and standard Ingress for traffic routing.
- Implements WAF and DDoS protection using Cloud Armor.
- Sets up Container-Native Load Balancing via NEGs.
- Manages Google-managed SSL certificates and TLS policies.
- Facilitates Private Service Connect for cross-VPC service exposure.
- Troubleshoots load-balancer health checks and connection draining issues.
When to use it
- When setting up external or internal traffic routing for GKE applications.
- When securing GKE services with Cloud Armor or custom SSL policies.
- When migrating to or configuring the modern Kubernetes Gateway API.
- When diagnosing 502/5xx errors or backend health-check failures.
- When optimizing traffic for latency using Topology Aware Routing.
Advantages
- Provides standardized manifest templates for common networking configurations.
- Simplifies complex GKE networking tasks like NEG configuration.
- Offers clear troubleshooting paths for common load-balancer issues.
- Supports modern Kubernetes Gateway API standards.
Usage examples
- “How do I configure weighted traffic splitting for a canary deployment using the Gateway API?”
- The agent provides an HTTPRoute manifest template with weighted backendRefs and explains how to apply it to split traffic between two service versions.
- “My GKE Ingress is returning 502 errors, how can I troubleshoot this?”
- The agent guides you through checking health-check source ranges, verifying backend health-check paths, and ensuring the service is using container-native load balancing.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/google/gke-service-networking/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip gke-service-networking.zip -d .agents/skills
Documentation by Google
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
CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="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 thegke-l7-global-external-managedGatewayClass with an HTTP listener.assets/httproute.yaml— HTTPRoute attaching to the Gateway viaparentRefsand routing a path prefix to a ServicebackendRef.assets/httproute-traffic-split.yaml— HTTPRoute demonstrating weighted traffic splitting (e.g. 90/10) for canary deployments across backend services.
kubectl apply -f assets/gateway.yaml
kubectl apply -f assets/httproute.yamlTraffic Splitting (Canary Deployments):
HTTPRoute supports weighted traffic splitting across multiple backend Services for canary rollouts:
spec:
rules:
- backendRefs:
- name: app-v1
port: 80
weight: 90
- name: app-v2
port: 80
weight: 102. 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.
Create a Security Policy in Cloud Armor:
gcloud compute security-policies create {security_policy_name} \ --description "WAF policy for {app_name}" # Example rule: block an abusive IP range gcloud compute security-policies rules create 1000 \ --security-policy {security_policy_name} \ --action deny-403 \ --src-ip-ranges "203.0.113.0/24" \ --description "Block abusive range"Reference it in a
BackendConfig:assets/backendconfig.yaml(setsspec.securityPolicy.name).Associate the
BackendConfigwith yourServicevia annotations:# In your Kubernetes Service manifest metadata.annotations: cloud.google.com/backend-config: '{"default": "{backend_config_name}"}' # Or for specific port mappings: cloud.google.com/backend-config: '{"ports": {"80": "{backend_config_name}"}}'
4. Configure Google-Managed SSL Certificates
Automatically provision and renew SSL certificates.
Legacy Ingress approach: apply assets/managed-certificate.yaml (a
ManagedCertificate listing your domains), then reference it in the Ingress
annotations:
networking.gke.io/managed-certificates: {certificate_name}Gateway API approach: for standard Certificate Manager integration, create a
CertificateMap and reference it in the Gateway metadata annotations using the
exact annotation networking.gke.io/certmap (spelled without any hyphens in
certmap):
metadata:
annotations:
networking.gke.io/certmap: {certificate_map_name}[!IMPORTANT] The annotation key is strictly
networking.gke.io/certmap(do not usecert-maporcertificate-map).
Alternatively, reference a Kubernetes Secret in the HTTPS listener's
tls.certificateRefs. Both variants are in assets/gateway-https.yaml.
5. Enable Container-Native Load Balancing (Recommended)
Container-native load balancing allows load balancers to target Kubernetes Pods directly, rather than targeting nodes. This improves latency and distribution.
Prerequisites: Cluster must be VPC-native.
How it works: the cloud.google.com/neg annotation on a Service triggers
creation of a NEG that mirrors the Pod IPs. GKE often adds it for you — but not
always, and knowing which case you are in is the whole point.
# In your Kubernetes Service manifest metadata.annotations:
cloud.google.com/neg: '{"ingress": true}'When the annotation is automatic (do not add it by hand):
Internal Ingress — container-native load balancing is always used, not optional. Internal Ingress always uses
GCE_VM_IP_PORTNEGs and requires a VPC-native cluster.External Ingress, but only when all four hold: the cluster is VPC-native, is not on Shared VPC, does not use GKE Network Policy, and has the
HttpLoadBalancingadd-on enabled (on by default — do not disable it). GKE then annotates Services automatically.
When you must add it explicitly:
Standalone NEGs — you manage the load balancer yourself instead of letting Ingress own it. Required if the LB must be configured outside GKE, since Ingress overwrites managed load balancer settings on sync or upgrade. You become responsible for every part of the load balancer.
Any external-Ingress cluster failing one of the four conditions above — Shared VPC, GKE Network Policy, or non-VPC-native. Enable per Service.
Legacy configurations — some older external Ingress objects created on VPC-native clusters still use instance group backends.
Not supported / no NEG fallback:
Windows Server node pools.
Routes-based (non-VPC-native) clusters with external Ingress — the Ingress controller falls back to unmanaged instance groups spanning all nodes.
Scale consequence: without NEGs a cluster is capped at 1,000 nodes, and non-NEG Services behind Ingress stop functioning correctly beyond that. With NEGs there is no GKE node limit.
6. Configure Private Service Connect (PSC)
Private Service Connect allows you to expose services in one VPC to consumers in another VPC securely, without VPC peering.
Prerequisite: The backing Service must be an internal passthrough Network
Load Balancer — i.e. type: LoadBalancer with the
networking.gke.io/load-balancer-type: "Internal" annotation. The
ServiceAttachment requires this; a ClusterIP or external LoadBalancer Service
will not work.
Steps:
Create an internal LoadBalancer Service for your workload.
Create a
ServiceAttachmentreferencing that Service:assets/service-attachment.yaml(setsconnectionPreference, the PSC NAT subnet, and the ServiceresourceRef).Share the
ServiceAttachmentURI with consumers to create a PSC endpoint in their VPC.
7. Topology Aware Routing (Cost & Latency Optimization)
To minimize cross-zone data transfer costs and network latency, configure Kubernetes Services with Topology Aware Routing. This routes traffic to Pods in the same zone as the originating client:
# In your Kubernetes Service manifest metadata.annotations:
service.kubernetes.io/topology-mode: autoTroubleshooting
Diagnose Ingress / load-balancer data-plane failures. These map to both Ingress
(BackendConfig / FrontendConfig) and Gateway (GCPBackendPolicy /
HealthCheckPolicy / GCPGatewayPolicy). Stay at the read-only → propose-manifest
boundary; never apply live mutations directly.
502 / 5xx with UNHEALTHY backends (health checks)
The Google Cloud load-balancer health check is separate from Kubernetes
liveness/readiness probes — it runs from outside the cluster, so a Pod can be
Ready while the backend service still shows UNHEALTHY.
Allow the Google health-check source ranges to the node/Pod serving port. GKE usually creates this rule automatically, but on Shared VPC or with hand-managed firewalls it can be missing:
gcloud compute firewall-rules create allow-lb-health-checks \ --allow tcp:SERVING_PORT \ --source-ranges 130.211.0.0/22,35.191.0.0/16 \ --target-tags NODE_TAGPoint the health check at a healthy endpoint. If the default
/returns a non-200, set a custom health check with aBackendConfig(Ingress) or aHealthCheckPolicy(Gateway):# BackendConfig (Ingress) spec: healthCheck: requestPath: /healthz port: 8080 checkIntervalSec: 15 timeoutSec: 5Confirm the Service is container-native (NEG) so the check targets Pod IPs rather than nodes (see workflow 5).
502 / dropped requests during rollouts or on long requests
Enable connection draining so in-flight requests finish before a backend Pod is removed during a rolling update or scale-down:
# BackendConfig (Ingress) spec: connectionDraining: drainingTimeoutSec: 60Raise the backend timeout for slow or streaming responses — a 502/408 on a request that runs longer than the backend response timeout is the classic symptom. Set
timeoutSecin theBackendConfig(Ingress) orGCPBackendPolicy(Gateway).
TLS / SSL handshake failures or weak-cipher enforcement
Ingress: attach an SSL policy (minimum TLS version / cipher profile) with a
FrontendConfigsslPolicy, and optionally force HTTP→HTTPS withredirectToHttps:# FrontendConfig (external Ingress only) spec: sslPolicy: gke-ingress-ssl-policy redirectToHttps: enabled: trueGateway: attach the SSL policy name in a
GCPGatewayPolicy. For a regional Gateway, create and reference a regional SSL policy.
Gotchas
Certificate Manager API must be enabled for the
networking.gke.io/certmapannotation to work (gcloud services enable certificatemanager.googleapis.com); without it the Gateway fails to provision the certificate map.Regional Gateway classes need a proxy-only subnet: classes like
gke-l7-regional-external-managedandgke-l7-rilbrequire a subnet with--purpose=REGIONAL_MANAGED_PROXYin the region; the Gateway stays unprogrammed without it.ManagedCertificate provisioning depends on DNS: the certificate stays in
Provisioninguntil the domain's A/AAAA records point at the load balancer IP, and can take 15-60 minutes after DNS is correct.
References
Files
- ATTRIBUTION.mdAdded by AutoGineer862 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md11.8 KiB
- assets/backendconfig.yaml288 B
- assets/gateway-https.yaml777 B
- assets/gateway.yaml495 B
- assets/httproute-traffic-split.yaml438 B
- assets/httproute.yaml452 B
- assets/ingress.yaml581 B
- assets/managed-certificate.yaml285 B
- assets/service-attachment.yaml527 B
- references/attribution.md1.9 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs a command-line tool, Needs Node.js
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Publisher
- Google (Official)
- Source
- google/skills · skills/cloud/gke-service-networking · commit 2194d3b
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Google.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download gke-service-networking.zip