Conformance on Gateway API

Levels

Mon, 01 Jan 0001 00:00:00 +0000

There are two levels of Gateway API conformance for implementations. These are determined based on the submission of conformance reports to the Gateway API repo.

Conformant

Conformant implementations have submitted at least one conformance report that:

All core conformance tests for at least one combination of Route type and Profile
All claimed Extended features for one of the two (2) most recent Gateway API releases.

So, it’s conformant to support Mesh + HTTPRoute, or Gateway + HTTPRoute, or Gateway + TLSRoute, or Gateway + Mesh + HTTPRoute, plus any extended features the implementation claims. But implementations must support at least one Profile and one Route type in that profile, and must pass all Core conformance tests for that Profile and Route type in addition to all claimed Extended features.

Running the suite

Mon, 01 Jan 0001 00:00:00 +0000

Running Tests

There are two main contrasting sets of conformance tests:

Gateway related tests (can also be thought of as ingress tests)
Service Mesh related tests

By default, the suite infers supported features from GatewayClass and XMesh status. To select features manually for development, use the -supported-features flag. When this flag is set, only the listed features are enabled.

We’ll cover each use case separately, but it’s also possible to combine these if your implementation implements both. There are also options which pertain to the entire test suite regardless of which tests you’re running.

Changelog

Mon, 01 Jan 0001 00:00:00 +0000

This page lists changes made to the Gateway API conformance process, descending by version. Only versions that included changes to conformance are listed.

Gateway API v1.6

Stale category removed.

As of this version:

If the current release of Gateway API is version n:

Implementations that submitted reports for version n or n-1 may be Conformant if they meet the other requirements.
Implementation that submitted reports for version n-2 may only be Partially Conformant, even they meet all other criteria for conformance.
Implememtations that submitted reports for version n-3 or older, are no longer conformant.

Gateway API v1.3

Stale category introduced.

As of this version: