diff --git a/conformance/results/cilium.yaml b/conformance/reports/v0.7.1/cilium-cilium.yaml similarity index 100% rename from conformance/results/cilium.yaml rename to conformance/reports/v0.7.1/cilium-cilium.yaml diff --git a/conformance/results/istio.yaml b/conformance/reports/v0.7.1/istio.io-istio.yaml similarity index 86% rename from conformance/results/istio.yaml rename to conformance/reports/v0.7.1/istio.io-istio.yaml index 7346aedf4d..4a41612f80 100644 --- a/conformance/results/istio.yaml +++ b/conformance/reports/v0.7.1/istio.io-istio.yaml @@ -1,6 +1,6 @@ apiVersion: gateway.networking.k8s.io/v1alpha1 date: "2023-07-24T14:26:14-07:00" -gatewayAPIVersion: 4c436290f2bfeaeaf0b1a367449e16de3e0addc4 +gatewayAPIVersion: 4c436290f2bfeaeaf0b1a367449e16de3e0addc4 # making an exception to the version for this release, since this was the first release we started submitting reports for. implementation: contact: - '@istio/maintainers' diff --git a/conformance/results/kong-kubernetes-ingress-controller.yaml b/conformance/reports/v0.7.1/kong-kubernetes-ingress-controller.yaml similarity index 100% rename from conformance/results/kong-kubernetes-ingress-controller.yaml rename to conformance/reports/v0.7.1/kong-kubernetes-ingress-controller.yaml diff --git a/conformance/results/kuma.yaml b/conformance/reports/v0.7.1/kumahq-kuma.yaml similarity index 100% rename from conformance/results/kuma.yaml rename to conformance/reports/v0.7.1/kumahq-kuma.yaml diff --git a/conformance/reports/v0.7.1/latest b/conformance/reports/v0.7.1/latest new file mode 120000 index 0000000000..b9bc2fdcb1 --- /dev/null +++ b/conformance/reports/v0.7.1/latest @@ -0,0 +1 @@ +latest \ No newline at end of file diff --git a/conformance/results/nginx-kubernetes-gateway.yaml b/conformance/reports/v0.7.1/nginxinc-nginx-kubernetes-gateway.yaml similarity index 100% rename from conformance/results/nginx-kubernetes-gateway.yaml rename to conformance/reports/v0.7.1/nginxinc-nginx-kubernetes-gateway.yaml diff --git a/conformance/results/contour.yaml b/conformance/reports/v0.7.1/projectcontour-contour.yaml similarity index 84% rename from conformance/results/contour.yaml rename to conformance/reports/v0.7.1/projectcontour-contour.yaml index 85b86c9937..dda1917751 100644 --- a/conformance/results/contour.yaml +++ b/conformance/reports/v0.7.1/projectcontour-contour.yaml @@ -1,6 +1,6 @@ apiVersion: gateway.networking.k8s.io/v1alpha1 date: "2023-07-25T22:11:56Z" -gatewayAPIVersion: "e9859d057b43d177176a9d3d6b15dbdd27fe7e46" +gatewayAPIVersion: "e9859d057b43d177176a9d3d6b15dbdd27fe7e46" # making an exception to the version for this release, since this was the first release we started submitting reports for. implementation: contact: - '@projectcontour/maintainers' diff --git a/geps/gep-1709.md b/geps/gep-1709.md index 74d7593d9a..336c733700 100644 --- a/geps/gep-1709.md +++ b/geps/gep-1709.md @@ -522,12 +522,28 @@ profiles: Implementers can submit their reports upstream by creating a pull request to the Gateway API repository and adding new reports to a file specific to their -implementation's project name: +implementation's organization and project name: ```console -conformance/results/-.yaml +conformance/reports//-.yaml ``` +The `` directory in the above refers to the version of Gateway API. The +`latest` release will include a symlink that points to the latest version +directory. + +For instance: + +```console +conformance/reports/v0.7.1/acme-operator.yaml +``` + +> **NOTE**: Implementations **MUST** report for a specific release version +> (e.g. `v0.7.1`) and not use branches or Git SHAs. Some exceptions will be +> made for initial reports to help make it easier for implementations to get +> started, but as we move to standard everyone should be reporting on specific +> releases. + Creating a pull request to add the `ConformanceReport` will start the [certification process](#certification-process).