Submit conformance report for GKE Gateway (#4214)

Author: kl52752

conformance/reports/v1.4.0/gke-gateway/README.md

@@ -0,0 +1,37 @@
+# GKE (Google Kubernetes Engine) Gateway
+
+## Table of Contents
+
+|API channel|Implementation version|Mode|Report|
+|-----------|----------------------|----|------|
+|standard|1.34.1-gke.1829001|gke-l7-regional-external-managed|[v1.34.1 rxlb report](./standard-1.43.1-rxlb-report.yaml)|
+
+## Reproduce
+
+GKE Gateway conformance report can be reproduced by the following steps.
+
+1. create a GKE cluster with Gateway API enabled (the minimum cluster version that supports v1.4.0 CRD is `1.34.1-gke.1829001`)
+
+```
+gcloud container clusters create "${cluster_name}" --gateway-api=standard --location="${location} --cluster-version={$version}"
+```
+
+2. create a proxy-only subnet if using a regional Gateway following [guide](https://cloud.google.com/kubernetes-engine/docs/how-to/deploying-gateways#configure_a_proxy-only_subnet)
+
+3. run the following command from within the [GKE Gateway repo](https://github.com/GoogleCloudPlatform/gke-gateway-api)
+
+```
+go test ./conformance -run TestConformance -v -timeout=3h -args \
+    --gateway-class=gke-l7-regional-external-managed \
+    --conformance-profiles=GATEWAY-HTTP \
+    --organization=GKE \
+    --project=gke-gateway \
+    --url=https://cloud.google.com/kubernetes-engine/docs/concepts/gateway-api \
+    --version=1.34.1-gke.1829001 \
+    --contact=gke-gateway-dev@google.com \
+    --skip-tests=HTTPRouteHostnameIntersection \
+    --supported-features=Gateway,HTTPRoute,GatewayPort8080,HTTPRouteHostRewrite,HTTPRoutePathRedirect,HTTPRouteRequestMirror,HTTPRouteRequestPercentageMirror,HTTPRouteResponseHeaderModification,HTTPRouteSchemeRedirect \
+    --report-output="/path/to/report"
+```
+
+Note: the repro result can be flaky in some cases because the conformance framework doesn't isolate test cases enough.

conformance/reports/v1.4.0/gke-gateway/standard-1.43.1-rxlb-report.yaml

@@ -0,0 +1,62 @@
+apiVersion: gateway.networking.k8s.io/v1
+date: "2025-10-31T09:24:35Z"
+gatewayAPIChannel: standard
+gatewayAPIVersion: v1.4.0
+implementation:
+  contact:
+  - gke-gateway-dev@google.com
+  organization: GKE
+  project: gke-gateway
+  url: https://cloud.google.com/kubernetes-engine/docs/concepts/gateway-api
+  version: 1.34.1-gke.1829001
+kind: ConformanceReport
+mode: default
+profiles:
+- core:
+    result: partial
+    skippedTests:
+    - HTTPRouteHostnameIntersection
+    statistics:
+      Failed: 0
+      Passed: 32
+      Skipped: 1
+  extended:
+    result: success
+    statistics:
+      Failed: 0
+      Passed: 7
+      Skipped: 0
+    supportedFeatures:
+    - GatewayPort8080
+    - HTTPRouteHostRewrite
+    - HTTPRoutePathRedirect
+    - HTTPRouteRequestMirror
+    - HTTPRouteRequestPercentageMirror
+    - HTTPRouteResponseHeaderModification
+    - HTTPRouteSchemeRedirect
+    unsupportedFeatures:
+    - GatewayAddressEmpty
+    - GatewayHTTPListenerIsolation
+    - GatewayInfrastructurePropagation
+    - GatewayStaticAddresses
+    - HTTPRoute303RedirectStatusCode
+    - HTTPRoute307RedirectStatusCode
+    - HTTPRoute308RedirectStatusCode
+    - HTTPRouteBackendProtocolH2C
+    - HTTPRouteBackendProtocolWebSocket
+    - HTTPRouteBackendRequestHeaderModification
+    - HTTPRouteBackendTimeout
+    - HTTPRouteCORS
+    - HTTPRouteDestinationPortMatching
+    - HTTPRouteMethodMatching
+    - HTTPRouteNamedRouteRule
+    - HTTPRouteParentRefPort
+    - HTTPRoutePathRewrite
+    - HTTPRoutePortRedirect
+    - HTTPRouteQueryParamMatching
+    - HTTPRouteRequestMultipleMirrors
+    - HTTPRouteRequestTimeout
+  name: GATEWAY-HTTP
+  summary: Core tests partially succeeded with 1 test skips. Extended tests succeeded.
+succeededProvisionalTests:
+- HTTPRouteRequestPercentageMirror

site-src/implementations.md

@@ -6,7 +6,7 @@ and provides status and resource references for them.
 Implementors and integrators of Gateway API are encouraged to update this
 document with status information about their implementations, the versions they
 cover, and documentation to help users get started. This status information should
-be no longer than a few paragraphs. 
+be no longer than a few paragraphs.
 
 ## Conformance levels
 
@@ -19,7 +19,7 @@ These implementations have submitted at least one conformance report that has pa
   * All core conformance tests for at least one combination of Route type and
     Profile
   * All claimed Extended features
-  
+
 for one of the two (2) most recent Gateway API releases.
 
 So, it's conformant to support Mesh + HTTPRoute, or Gateway + HTTPRoute, or
@@ -386,7 +386,7 @@ Google Cloud Service Mesh supports [Envoy-based sidecar mesh][envoy-sidecar-mesh
 
 ### Google Kubernetes Engine
 
-[![Conformance](https://img.shields.io/badge/Gateway_API_Partial_Conformance_v1.3.0-Google_Kubernetes_Engine-orange)](https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/reports/v1.3.0/gke-gateway)
+[![Conformance](https://img.shields.io/badge/Gateway_API_Partial_Conformance_v1.3.0-Google_Kubernetes_Engine-orange)](https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/reports/v1.4.0/gke-gateway)
 
 [Google Kubernetes Engine (GKE)][gke] is a managed Kubernetes platform offered
 by Google Cloud. GKE's implementation of the Gateway API is through the [GKE
@@ -399,7 +399,7 @@ advanced routing, multi-cluster load balancing and more. See the docs to deploy
 Gateways][gke-multi-cluster-gateway].
 
 The GKE Gateway controller passes all the core Gateway API conformance tests in the
-v1.3.0 release for the GATEWAY_HTTP conformance profile except `HTTPRouteHostnameIntersection`.
+v1.4.0 release for the GATEWAY_HTTP conformance profile except `HTTPRouteHostnameIntersection`.
 
 [gke]:https://cloud.google.com/kubernetes-engine
 [gke-gateway]:https://cloud.google.com/kubernetes-engine/docs/concepts/gateway-api
@@ -740,7 +740,7 @@ Page review timeline, starting with the v1.3 Page Review:
   any implementations that are are still Stale (after a right-of-reply period).
 * Gateway API v1.5 release Page Review (at least one month after the actual
   release): We will remove the Stale category, and implementation maintainers
-  will need to be at least partially conformant on each review, or during the 
+  will need to be at least partially conformant on each review, or during the
   right-of-reply period, or be removed from the implementations page.
 
 This means that, after the Gateway API v1.5 release, implementations cannot be