Unreleased documentation. Choose your installed release in the version menu. Features described here may be absent from that release.
Gateway API conformance evidence¶
Use the Gateway API reference to check supported features and configuration. Conformance reports provide test results for a specific HAPTIC and Gateway API version, including skipped tests and limits.
Coverage¶
The report contains three profiles. Extended results may be partial; inspect the named skipped tests and unsupported features before relying on an extension.
| Surface | Evidence and limits |
|---|---|
| HTTPRoute | GATEWAY-HTTP core and extended results |
| GRPCRoute | GATEWAY-GRPC core and extended results |
| TLSRoute | GATEWAY-TLS core and extended results |
| TCPRoute | HAPTIC's separate end-to-end tests; no profile in this report |
| Independent backend certificate SAN matching | BackendTLSPolicySANValidation remains skipped because HAProxy verifies the SNI hostname; unsupported policy identities are rejected |
Mesh and UDPRoute |
Unsupported; excluded from the declared feature set |
The backend identity limit is tracked in HAProxy issue 3452.
Find evidence for your release¶
Check the Gateway API implementations listing for an accepted report matching your HAPTIC and Gateway API versions. A report for another version doesn't establish coverage for your installation.
For a release published by GitHub Actions, download its
gateway-conformance-<version>-<run>-<attempt>.tar.gz asset from
GitHub Releases.
The release workflow attaches it after the conformance job succeeds. The archive contains:
report.yamllists the tested profiles, supported features, and skipped tests.provenance.jsonidentifies the tested release and environment. Itsverifiedandrelease_evidencefields must both betrue.SHA256SUMScontains checksums for those files.
Releases up to 0.5.0 were published from GitLab CI and have no conformance archive. An absent report doesn't establish conformance.
A manual conformance report job tests a development candidate, not a published release. A local artifact or passing regression test doesn't establish upstream acceptance; use the implementations listing for that.