domains / families / devops / gke-service-networking

gke-service-networking

separate

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).

When to use

• Configuring Gateway API manifests
• Configuring standard Ingress
• Configuring Cloud Armor WAF security policies
• Configuring Container-Native Load Balancing (NEGs)
• Configuring Private Service Connect (PSC)
• Configuring Google-managed SSL certificates
• Troubleshooting Ingress and load-balancer 502/5xx errors
• Troubleshooting backend health-check failures

When not to use

• Core cluster IP planning
• Dataplane V2 network policies
• Node NAT egress

Skill page

Source