gke-service-networking skillA
gke-service-networking is agent-read markdown (skill) from gke-labs/kube-agents: 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. Don't use for core cluster IP planning, Dataplane V2 network policies, or node NAT egress (use gke-networking instead)..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# GKE Service Networking Skill
This skill provides workflows for exposing applications running on GKE securely
to the internet or internal networks.
## 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 in GKE 1.24+).
**Example Gateway Manifest:**
```yaml
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
name: {gateway_name}
namespace: {namespace}
spec:
gatewayClassName: gke-l7-global-external-managed # GKE managed external L7 load balancer
listeners:
- name: http
protocol: HTTP
port: 80
```
**Example HTTPRoute Manifest:**
```yaml
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: {route_name}
namespace: {namespace}
spec:
parentRefs:
- name: {gateway_name}
rules:
- matches:
- path:
type: PathPrefix
value: /
backendRefs:
- name: {service_name}
port: 80
```
### 2. Configure Standard GKE Ingress
Use standard Ingress for simpler use cases or legacy setups.
**Example Ingress Manifest:**
```yaml
…Read the whole file at its exact version.
How to install
mdr add gke-labs/kube-agents/gke-service-networking@git:20260807.d47bdf1mdr add gke-labs/kube-agents/gke-service-networking@sha256:a94983d97d1a368dPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_d7fxl2ye2cw574su)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6110 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
gke-labs/kube-agents · 64 stars · license Apache-2.0 · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_d7fxl2ye2cw574su GET https://markdownregistry.com/api/v1/resolve?ref=gke-labs/kube-agents/gke-service-networking GET https://markdownregistry.com/api/v1/blob/a94983d97d1a368dd99559f6326706dd7ca82ad787ce3278d4d18a606ac8f77c
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.