KIngress conformance test checklist for Contour
carlisia opened this issue · comments
This checklist tracks that all Knative KIngress e2e conformance tests for this Gateway API implementation are passing.
- basics/TestBasics
- basics/TestBasicsHTTP2
- grpc/TestGRPC
- grpc/TestGRPCSplit
- headers/tags/TestTagHeaders
- headers/TestProbeHeaders
- headers/TestPreSplitSetHeaders
- headers/TestPostSplitSetHeaders
- host-rewrite/TestRewriteHost (#533)
- hosts/TestMultipleHosts
- httpoption/TestHTTPOption
- dispatch/TestPath
- dispatch/TestPercentage
- dispatch/TestPathAndPercentageSplit
- dispatch/TestRule
- retry/TestRetry
- timeout/TestTimeout
- tls/TestIngressTLS
- update/TestUpdate
- visibility/TestVisibility
- visibility/TestVisibilitySplit
- visibility/TestVisibilityPath
- ingressclass/TestIngressClass
- websocket/TestWebsocket
- websocket/TestWebsocketSplit
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
This issue or pull request is stale because it has been open for 90 days with no activity.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle rotten - Close this issue or PR with
/close
/lifecycle stale
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
/remove-lifecycle stale
/lifecycle frozen
contour supports gRPCRoute (on main) now if that is sufficient to try out the grpc tests!
@sunjayBhatia we don't create GRPCRoutes unfortunately and I don't think it makes sense for Knative to do so.
Revision updates can change the backend protocol so we're hoping to just use HTTPRoute and then rely on this GEP kubernetes-sigs/gateway-api#1979 as a way to signal the backend protocol.
As of projectcontour/contour@d802a88 Contour now supports websocket upgrades on Gateway API generated routes
Closing this - we are tracking this in the repo and eventually we'll have tests that run continously - see #621