conformance: Update the Gloo Gateway project's published 1.0.0 reports

conformance/reports/v1.0.0/gloo-gateway/README.md

@@ -4,6 +4,15 @@
 
 |API channel|Implementation version|Mode|Report|
 |-----------|----------------------|----|------|
-|x|[v2.0.0-beta1](https://github.com/solo-io/gloo/releases/tag/v2.0.0-beta1)|x|[link](./v2.0.0-beta1-report.yaml)|
+|x|[v1.17.4](https://github.com/solo-io/gloo/releases/tag/v1.17.4)|x|[link](./v1.17.4-report.yaml)|
 
 ## Reproduce
+
+> Note: [this is a mirror of the steps outlined in the conformance GHA workflow](https://github.com/solo-io/gloo/blob/main/.github/workflows/composite-actions/kube-gateway-api-conformance-tests/action.yaml).
+
+1. Checkout the repository: `git clone https://github.com/solo-io/gloo && cd gloo`
+2. Export the VERSION environment variable: `export VERSION="1.17.4"`
+3. Create a kind cluster: `SKIP_DOCKER="true" CONFORMANCE="true" IMAGE_VARIANT="standard" CLUSTER_NODE_VERSION="v1.29.2@sha256:51a1434a5397193442f0be2a297b488b6c919ce8a3931be0ce822606ea5ca245" ./ci/kind/setup-kind.sh`
+4. Install the Gloo Gateway helm chart with the Gateway API extension enabled: `helm upgrade -i --create-namespace -n gloo-system gloo gloo/gloo --version $VERSION --set kubeGateway.enabled=true`
+5. Run the conformance suite locally: `make conformance-experimental`
+6. Verify the conformance report: `cat _test/conformance/1.17.4-report.yaml`

conformance/reports/v1.0.0/gloo-gateway/v2.0.0-beta1-report.yaml → conformance/reports/v1.0.0/gloo-gateway/v1.17.4-report.yaml

@@ -1,14 +1,13 @@
 apiVersion: gateway.networking.k8s.io/v1alpha1
-date: "2023-11-06T16:11:11Z"
+date: "2024-08-21T19:31:55Z"
 gatewayAPIVersion: v1.0.0
 implementation:
   contact:
-  - eitan@solo.io
-  - yuval@solo.io
+  - github.com/solo-io/gloo/issues/new/choose
   organization: solo.io
   project: gloo-gateway
   url: github.com/solo-io/gloo
-  version: v2.0.0-beta1
+  version: v1.17.4
 kind: ConformanceReport
 profiles:
 - core:
@@ -22,21 +21,21 @@ profiles:
     result: success
     statistics:
       Failed: 0
-      Passed: 6
+      Passed: 9
       Skipped: 0
     summary: ""
     supportedFeatures:
-    - HTTPRoutePortRedirect
-    - HTTPRouteSchemeRedirect
-    - HTTPRoutePathRedirect
+    - HTTPRouteRequestMirror
     - HTTPRouteQueryParamMatching
+    - HTTPRoutePathRedirect
     - HTTPRouteMethodMatching
-    - HTTPRouteResponseHeaderModification
-    unsupportedFeatures:
-    - HTTPRouteRequestMirror
-    - HTTPRouteRequestTimeout
+    - HTTPRouteSchemeRedirect
     - HTTPRouteHostRewrite
+    - HTTPRoutePortRedirect
     - HTTPRoutePathRewrite
+    - HTTPRouteResponseHeaderModification
+    unsupportedFeatures:
     - HTTPRouteRequestMultipleMirrors
     - HTTPRouteBackendTimeout
+    - HTTPRouteRequestTimeout
   name: HTTP

site-src/implementations.md

@@ -25,7 +25,7 @@ cover, and documentation to help users get started.
 - [Emissary-Ingress (Ambassador API Gateway)][4] (alpha)
 - [Envoy Gateway][18] (GA)
 - [Flomesh Service Mesh][17] (beta)
-- [Gloo Gateway 2.0][5] (beta)
+- [Gloo Gateway][5] (GA)
 - [Google Kubernetes Engine][6] (GA)
 - [HAProxy Ingress][7] (alpha)
 - [HAProxy Kubernetes Ingress Controller][32] (GA)
@@ -243,9 +243,9 @@ FSM support of Gateway API is built on top [Flomesh Gateway API](fgw) and it cur
 [![Conformance](https://img.shields.io/badge/Gateway%20API%20Conformance%20v1.0.0-GlooGateway-green)](https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/reports/v1.0.0/gloo-gateway)
 
 [Gloo Gateway][gloogateway] by [Solo.io][solo] is a feature-rich, Kubernetes-native ingress controller and next-generation API gateway.
-Gloo Gateway 2.0 brings the full power and community support of Gateway API to its existing control-plane implementation.
+Gloo Gateway brings the full power and community support of Gateway API to its existing control-plane implementation.
 
-[gloogateway]:https://docs.solo.io/gloo-gateway/v2
+[gloogateway]:https://docs.solo.io/gateway/latest/
 [solo]:https://www.solo.io
 
 ### Google Kubernetes Engine
@@ -421,7 +421,7 @@ STUNner currently supports version `v1alpha2` of the Gateway API specification.
 [Traefik Proxy][traefik-proxy] is an open source cloud-native application proxy.
 
 Traefik Proxy currently supports version `v1.1.0` of the Gateway API specification, check the [Kubernetes Gateway Provider Documentation][traefik-proxy-gateway-api-doc] for more information on how to deploy and use it.
-Traefik Proxy's implementation passes all HTTP core and some extended conformance tests, but also supports the TCPRoute and TLSRoute features from the Experimental channel. 
+Traefik Proxy's implementation passes all HTTP core and some extended conformance tests, but also supports the TCPRoute and TLSRoute features from the Experimental channel.
 
 For help and support with Traefik Proxy, [create an issue][traefik-proxy-issue-new] or ask for help in the [Traefik Labs Community Forum][traefiklabs-community-forum].