Skip to content

update conformance report for EnvoyGateway v1.5.0 #3987

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Aug 13, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 17 additions & 4 deletions conformance/reports/v1.3.0/envoy-gateway/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,17 @@

## Table of Contents

|API channel|Implementation version|Mode|Report|
|-----------|----------------------|----|------|
| experimental |[v1.4.0](https://github.com/envoyproxy/gateway/releases/tag/v1.4.0)| default |[link](./experimental-v1.4.0-default-report.yaml)|
| API channel | Implementation version | Mode | Report |
|--------------|---------------------------------------------------------------------|------------------------------|------------------------------------------------------------------|
| experimental | [v1.5.0](https://github.com/envoyproxy/gateway/releases/tag/v1.5.0) | ControllerNamespace(default) | [link](./experimental-v1.5.0-default-report.yaml) |
| experimental | [v1.5.0](https://github.com/envoyproxy/gateway/releases/tag/v1.5.0) | GatewayNamespace | [link](./experimental-v1.5.0-gateway-namespace-mode-report.yaml) |


## Overview

Envoy Gateway supports different deployment [modes](https://gateway.envoyproxy.io/docs/tasks/operations/deployment-mode/#supported-modes),
including a controller namespace mode(the default one) and a [gateway namespace mode](https://gateway.envoyproxy.io/docs/tasks/operations/deployment-mode/#gateway-namespace-mode).
The conformance tests are run against both modes to ensure compatibility and functionality.

## Reproduce

Expand All @@ -23,8 +31,13 @@

3. Run the conformance tests

```bash
KUBE_DEPLOY_PROFILE=default CONFORMANCE_REPORT_PATH=conformance-report-k8s.yaml make experimental-conformance
```
or

```bash
CONFORMANCE_REPORT_PATH=conformance-report-k8s.yaml make experimental-conformance
KUBE_DEPLOY_PROFILE=gateway-namespace-mode CONFORMANCE_REPORT_PATH=conformance-report-k8s.yaml make experimental-conformance
```

4. Check the produced report
Expand Down
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
apiVersion: gateway.networking.k8s.io/v1
date: "2025-05-14T03:12:24Z"
date: "2025-08-08T05:23:48Z"
gatewayAPIChannel: experimental
gatewayAPIVersion: v1.3.0
implementation:
Expand All @@ -8,18 +8,10 @@ implementation:
organization: envoyproxy
project: envoy-gateway
url: https://github.com/envoyproxy/gateway
version: latest
version: v1.5.0
kind: ConformanceReport
mode: default
profiles:
- core:
result: success
statistics:
Failed: 0
Passed: 12
Skipped: 0
name: GATEWAY-GRPC
summary: Core tests succeeded.
- core:
result: success
statistics:
Expand Down Expand Up @@ -67,5 +59,13 @@ profiles:
Skipped: 0
name: GATEWAY-TLS
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldnt GATEWAY-TLS and GATEWAY-GRPC have the supportedFeatures section as well ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is just because the only tests in those profiles are "Core" - there are no tests of extended features for GRPCRoute or TLSRoute.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah thanks

summary: Core tests succeeded.
- core:
result: success
statistics:
Failed: 0
Passed: 12
Skipped: 0
name: GATEWAY-GRPC
summary: Core tests succeeded.
succeededProvisionalTests:
- HTTPRouteRequestPercentageMirror
Original file line number Diff line number Diff line change
@@ -0,0 +1,98 @@
apiVersion: gateway.networking.k8s.io/v1
date: "2025-08-08T05:25:57Z"
gatewayAPIChannel: experimental
gatewayAPIVersion: v1.3.0
implementation:
contact:
- https://github.com/envoyproxy/gateway/blob/main/GOVERNANCE.md
organization: envoyproxy
project: envoy-gateway
url: https://github.com/envoyproxy/gateway
version: v1.5.0
kind: ConformanceReport
mode: GatewayNamespace
profiles:
- core:
result: success
statistics:
Failed: 0
Passed: 12
Skipped: 0
extended:
result: success
statistics:
Failed: 0
Passed: 1
Skipped: 0
supportedFeatures:
- GatewayAddressEmpty
- GatewayHTTPListenerIsolation
- GatewayInfrastructurePropagation
- GatewayPort8080
unsupportedFeatures:
- GatewayStaticAddresses
name: GATEWAY-GRPC
summary: Core tests succeeded. Extended tests succeeded.
- core:
result: success
statistics:
Failed: 0
Passed: 33
Skipped: 0
extended:
result: success
statistics:
Failed: 0
Passed: 24
Skipped: 0
supportedFeatures:
- GatewayAddressEmpty
- GatewayHTTPListenerIsolation
- GatewayInfrastructurePropagation
- GatewayPort8080
- HTTPRouteBackendProtocolH2C
- HTTPRouteBackendProtocolWebSocket
- HTTPRouteBackendRequestHeaderModification
- HTTPRouteBackendTimeout
- HTTPRouteDestinationPortMatching
- HTTPRouteHostRewrite
- HTTPRouteMethodMatching
- HTTPRouteParentRefPort
- HTTPRoutePathRedirect
- HTTPRoutePathRewrite
- HTTPRoutePortRedirect
- HTTPRouteQueryParamMatching
- HTTPRouteRequestMirror
- HTTPRouteRequestMultipleMirrors
- HTTPRouteRequestPercentageMirror
- HTTPRouteRequestTimeout
- HTTPRouteResponseHeaderModification
- HTTPRouteSchemeRedirect
unsupportedFeatures:
- GatewayStaticAddresses
name: GATEWAY-HTTP
summary: Core tests succeeded. Extended tests succeeded.
- core:
result: success
statistics:
Failed: 0
Passed: 11
Skipped: 0
extended:
result: success
statistics:
Failed: 0
Passed: 1
Skipped: 0
supportedFeatures:
- GatewayAddressEmpty
- GatewayHTTPListenerIsolation
- GatewayInfrastructurePropagation
- GatewayPort8080
unsupportedFeatures:
- GatewayStaticAddresses
name: GATEWAY-TLS
summary: Core tests succeeded. Extended tests succeeded.
succeededProvisionalTests:
- GatewayInfrastructure
- HTTPRouteRequestPercentageMirror