Issues

• Provisioning follow-ups from #624

  gke-labs/gateway-api-reference-implementation#639 · Filter by author justinsb opened on Oct 7, 2026

• Central config distribution: data-plane pods should not need cluster-wide read access

  gke-labs/gateway-api-reference-implementation#637 · Filter by author justinsb opened on Oct 6, 2026

• Pass GatewayInfrastructure conformance test

  gke-labs/gateway-api-reference-implementation#635 · Filter by author justinsb opened on Oct 6, 2026

• Pass GatewayHTTPListenerIsolation conformance test

  gke-labs/gateway-api-reference-implementation#634 · Filter by author justinsb opened on Oct 6, 2026
  

• Pass GatewayWithAttachedRoutes and GatewayWithAttachedRoutesWithPort8080 conformance tests

  gke-labs/gateway-api-reference-implementation#633 · Filter by author justinsb opened on Oct 6, 2026
  

• State.Start runs the initial recompute twice

  gke-labs/gateway-api-reference-implementation#632 · Filter by author justinsb opened on Oct 6, 2026
  

• snigateway: measure and reduce tunnel overhead (TCP pool vs QUIC; CPU per byte)

  gke-labs/gateway-api-reference-implementation#621 · Filter by author justinsb opened on Oct 5, 2026

• snigateway: QUIC tunnel transport for TCP connections, with TCP pool fallback

  gke-labs/gateway-api-reference-implementation#610 · Filter by author justinsb opened on Oct 4, 2026
  1

  

• snigateway: route QUIC / HTTP/3 by SNI over a datagram tunnel

  gke-labs/gateway-api-reference-implementation#609 · Filter by author justinsb opened on Oct 4, 2026
  1

• Separate Gateway provisioning from the GARI data plane (garigateway, snigateway)

  gke-labs/gateway-api-reference-implementation#587 · Filter by author justinsb opened on Oct 3, 2026
  1