Skip to content
Open
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
48 changes: 48 additions & 0 deletions conformance/reports/v1.3.0/projectcontour-contour/README.md
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
Original file line number Diff line number Diff line change
@@ -0,0 +1,99 @@
apiVersion: gateway.networking.k8s.io/v1
date: "2025-11-13T13:49:19-05:00"
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: 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: partial
skippedTests:
- HTTPRouteHTTPSListener
Copy link
Member Author

Choose a reason for hiding this comment

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

had to leave this as a skipped test since there is not a specific enough feature to disable this one test (otherwise we would have to disable testing HTTPRoute in general), this should be addressed in the next release however to remove the skip entirely

statistics:
Failed: 0
Passed: 32
Skipped: 1
extended:
result: success
statistics:
Failed: 0
Passed: 19
Skipped: 0
supportedFeatures:
- GatewayAddressEmpty
- GatewayHTTPListenerIsolation
- GatewayInfrastructurePropagation
- GatewayPort8080
- HTTPRouteBackendProtocolH2C
- HTTPRouteBackendProtocolWebSocket
- HTTPRouteBackendRequestHeaderModification
- HTTPRouteBackendTimeout
- HTTPRouteDestinationPortMatching
- HTTPRouteHostRewrite
- HTTPRouteMethodMatching
- HTTPRoutePathRedirect
- HTTPRoutePathRewrite
- HTTPRouteQueryParamMatching
- HTTPRouteRequestMirror
- HTTPRouteRequestMultipleMirrors
- HTTPRouteRequestTimeout
- HTTPRouteResponseHeaderModification
- HTTPRouteSchemeRedirect
unsupportedFeatures:
- GatewayStaticAddresses
- HTTPRouteParentRefPort
- HTTPRoutePortRedirect
Copy link
Member Author

Choose a reason for hiding this comment

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

note: passing HTTPRouteParentRefPort and HTTPRoutePortRedirect as unsupported means we're now skipping running some tests that do pass, the specific tests that were previously skipped are HTTPRouteRedirectPortAndScheme and HTTPRouteInvalidParentRefSectionNameNotMatchingPort

- HTTPRouteRequestPercentageMirror
name: GATEWAY-HTTP
summary: Core tests partially succeeded with 1 test skips. 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
10 changes: 5 additions & 5 deletions site-src/implementations.md
Original file line number Diff line number Diff line change
Expand Up @@ -286,22 +286,22 @@ effort, check out the #development channel or join our [weekly developer meeting

### Contour

[![Conformance](https://img.shields.io/badge/Gateway%20API%20Conformance%20v1.2.1-Contour-green)](https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/reports/v1.2.1/projectcontour-contour)
[![Conformance](https://img.shields.io/badge/Gateway%20API%20Conformance%20v1.3.0-Contour-green)](https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/reports/v1.3.0/projectcontour-contour)

[Contour][contour] is a CNCF open source Envoy-based ingress controller for Kubernetes.

Contour [v1.31.0][contour-release] implements Gateway API v1.2.1.
Contour [v1.33.0][contour-release] implements Gateway API v1.3.0.
All [Standard channel][contour-standard] v1 API group resources (GatewayClass, Gateway, HTTPRoute, ReferenceGrant), plus most v1alpha2 API group resources (TLSRoute, TCPRoute, GRPCRoute, ReferenceGrant, and BackendTLSPolicy) are supported.
Contour's implementation passes most core extended Gateway API conformance tests included in the v1.2.1 release.
Contour's implementation passes most core extended Gateway API conformance tests included in the v1.3.0 release.

See the [Contour Gateway API Guide][contour-guide] for information on how to deploy and use Contour's Gateway API implementation.

For help and support with Contour's implementation, [create an issue][contour-issue-new] or ask for help in the [#contour channel on Kubernetes slack][contour-slack].

[contour]:https://projectcontour.io
[contour-release]:https://github.com/projectcontour/contour/releases/tag/v1.30.0
[contour-release]:https://github.com/projectcontour/contour/releases/tag/v1.33.0
[contour-standard]:concepts/versioning.md#release-channels
[contour-guide]:https://projectcontour.io/docs/1.30/guides/gateway-api/
[contour-guide]:https://projectcontour.io/docs/1.33/guides/gateway-api/
[contour-issue-new]:https://github.com/projectcontour/contour/issues/new/choose
[contour-slack]:https://kubernetes.slack.com/archives/C8XRH2R4J

Expand Down