What problem does it solve?
Exposing applications running on Google Kubernetes Engine to the internet or internal networks requires coordinating many moving parts—Gateway API routes, Ingress, WAF policies, SSL certificates, load balancer backends, and private connectivity—and misconfiguring any of them leads to broken traffic, security gaps, or unexpected costs.
Core Features & Use Cases
- Gateway API and Ingress Templates: Deployable manifests for external Gateways, HTTPRoutes with weighted traffic splitting for canary rollouts, and standard GCE Ingress.
- Security and TLS: Cloud Armor WAF security policies via BackendConfig, Google-managed SSL certificates, and Certificate Manager integration through the networking.gke.io/certmap annotation.
- Load Balancing and Private Connectivity: Container-native load balancing with NEGs, Private Service Connect ServiceAttachments, and Topology Aware Routing for cost and latency optimization.
- Use Case: You need to expose a new GKE service publicly with HTTPS, a WAF policy, and a 90/10 canary split between two backend versions—apply the provided Gateway, HTTPRoute, BackendConfig, and certificate templates after replacing the placeholders.
Quick Start
Ask the agent to configure a GKE Gateway with an HTTPRoute, a Google-managed SSL certificate, and a Cloud Armor security policy for your service.