generated from kubernetes/kubernetes-template-project
-
Notifications
You must be signed in to change notification settings - Fork 597
Add conformance report for Contour 1.33.0 and Gateway API 1.3.0 #4076
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
Open
sunjayBhatia
wants to merge
1
commit into
kubernetes-sigs:main
Choose a base branch
from
sunjayBhatia:contour-1.33.0-conformance-report
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
48 changes: 48 additions & 0 deletions
48
conformance/reports/v1.3.0/projectcontour-contour/README.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,48 @@ | ||
| # Projectcontour Contour | ||
|
|
||
| ## Table of Contents | ||
|
|
||
| |API channel|Implementation version|Mode|Report| | ||
| |-----------|----------------------|----|------| | ||
| |experimental|[v1.33.0](https://github.com/projectcontour/contour/releases/tag/v1.33.0)|x|[v1.33.0 report](./experimental-v1.33.0-default-report.yaml)| | ||
|
|
||
| ## Reproduce | ||
|
|
||
| ### Prerequisites | ||
|
|
||
| Follow the Contour [contribution guide][0] documentation for setting up your local development environment, which includes ensuring `kubectl`, `docker`, `kinD`, and other tools are installed. | ||
|
|
||
| ### Steps | ||
|
|
||
| 1. Clone the Contour GitHub repository | ||
|
|
||
| ```bash | ||
| git clone https://github.com/projectcontour/contour && cd contour | ||
| ``` | ||
|
|
||
| 2. Check out the desired version | ||
|
|
||
| ```bash | ||
| export VERSION=v<x.y.z> | ||
| git checkout $VERSION | ||
| ``` | ||
|
|
||
| 3. Run the conformance tests | ||
|
|
||
| ```bash | ||
| export CONTOUR_E2E_IMAGE="ghcr.io/projectcontour/contour:$VERSION" | ||
| export GENERATE_GATEWAY_CONFORMANCE_REPORT="true" | ||
| make setup-kind-cluster run-gateway-conformance cleanup-kind | ||
| ``` | ||
|
|
||
| Note: you can omit the `cleanup-kind` target if you would prefer to keep the `kinD` cluster. | ||
|
|
||
| 4. Check the produced report | ||
|
|
||
| ```bash | ||
| cat gateway-conformance-report/projectcontour-contour-*.yaml | ||
| ``` | ||
|
|
||
| Note: you can set `GATEWAY_CONFORMANCE_REPORT_OUTDIR` before running the tests to customize the output location. | ||
|
|
||
| [0]: https://github.com/projectcontour/contour/blob/main/CONTRIBUTING.md#building-from-source |
106 changes: 106 additions & 0 deletions
106
conformance/reports/v1.3.0/projectcontour-contour/experimental-v1.33.0-default-report.yaml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,106 @@ | ||
| apiVersion: gateway.networking.k8s.io/v1 | ||
| date: "2025-09-09T14:48:38Z" | ||
| gatewayAPIChannel: experimental | ||
| gatewayAPIVersion: v1.3.0 | ||
| implementation: | ||
| contact: | ||
| - '@projectcontour/maintainers' | ||
| organization: projectcontour | ||
| project: contour | ||
| url: https://projectcontour.io/ | ||
| version: v1.33.0 | ||
| kind: ConformanceReport | ||
| mode: default | ||
| profiles: | ||
| - core: | ||
| result: success | ||
| statistics: | ||
| Failed: 0 | ||
| Passed: 11 | ||
| Skipped: 0 | ||
| extended: | ||
| result: partial | ||
| skippedTests: | ||
| - GatewayStaticAddresses | ||
| statistics: | ||
| Failed: 0 | ||
| Passed: 1 | ||
| Skipped: 1 | ||
| supportedFeatures: | ||
| - GatewayAddressEmpty | ||
| - GatewayHTTPListenerIsolation | ||
| - GatewayInfrastructurePropagation | ||
| - GatewayPort8080 | ||
| - GatewayStaticAddresses | ||
| name: GATEWAY-TLS | ||
| summary: Core tests succeeded. Extended tests partially succeeded with 1 test skips. | ||
| - core: | ||
| result: success | ||
| statistics: | ||
| Failed: 0 | ||
| Passed: 12 | ||
| Skipped: 0 | ||
| extended: | ||
| result: partial | ||
| skippedTests: | ||
| - GatewayStaticAddresses | ||
| statistics: | ||
| Failed: 0 | ||
| Passed: 1 | ||
| Skipped: 1 | ||
| supportedFeatures: | ||
| - GatewayAddressEmpty | ||
| - GatewayHTTPListenerIsolation | ||
| - GatewayInfrastructurePropagation | ||
| - GatewayPort8080 | ||
| - GatewayStaticAddresses | ||
| name: GATEWAY-GRPC | ||
| summary: Core tests succeeded. Extended tests partially succeeded with 1 test skips. | ||
| - core: | ||
| result: partial | ||
| skippedTests: | ||
| - HTTPRouteHTTPSListener | ||
| statistics: | ||
| Failed: 0 | ||
| Passed: 32 | ||
| Skipped: 1 | ||
| extended: | ||
| result: partial | ||
| skippedTests: | ||
| - GatewayStaticAddresses | ||
| - HTTPRouteInvalidParentRefSectionNameNotMatchingPort | ||
| - HTTPRouteRedirectPortAndScheme | ||
| statistics: | ||
| Failed: 0 | ||
| Passed: 21 | ||
| Skipped: 3 | ||
| supportedFeatures: | ||
| - GatewayAddressEmpty | ||
| - GatewayHTTPListenerIsolation | ||
| - GatewayInfrastructurePropagation | ||
| - GatewayPort8080 | ||
| - GatewayStaticAddresses | ||
| - HTTPRouteBackendProtocolH2C | ||
| - HTTPRouteBackendProtocolWebSocket | ||
| - HTTPRouteBackendRequestHeaderModification | ||
| - HTTPRouteBackendTimeout | ||
| - HTTPRouteDestinationPortMatching | ||
| - HTTPRouteHostRewrite | ||
| - HTTPRouteMethodMatching | ||
| - HTTPRouteParentRefPort | ||
| - HTTPRoutePathRedirect | ||
| - HTTPRoutePathRewrite | ||
| - HTTPRoutePortRedirect | ||
| - HTTPRouteQueryParamMatching | ||
| - HTTPRouteRequestMirror | ||
| - HTTPRouteRequestMultipleMirrors | ||
| - HTTPRouteRequestTimeout | ||
| - HTTPRouteResponseHeaderModification | ||
| - HTTPRouteSchemeRedirect | ||
| unsupportedFeatures: | ||
| - HTTPRouteRequestPercentageMirror | ||
| name: GATEWAY-HTTP | ||
| summary: Core tests partially succeeded with 1 test skips. Extended tests partially | ||
| succeeded with 3 test skips. | ||
| succeededProvisionalTests: | ||
| - GatewayInfrastructure | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of skipping tests can you just change the set of features you claim to support?