Skip to content
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.

Sign up for GitHub

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

Jump to bottom

KIngress e2e conformance test checklist for Istio #383

Closed
23 of 25 tasks
carlisia opened this issue Aug 23, 2022 · 4 comments
Closed
23 of 25 tasks

KIngress e2e conformance test checklist for Istio #383

carlisia opened this issue Aug 23, 2022 · 4 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@carlisia
Copy link
Member

carlisia commented Aug 23, 2022 •
edited by nak3
Loading

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 (Add HostRewrite Support #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
@github-actions
Copy link
Contributor

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.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 22, 2022
@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 23, 2022
@github-actions
Copy link
Contributor

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.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 24, 2023
@ReToCode
Copy link
Member

/lifecycle frozen

@knative-prow knative-prow bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 24, 2023
@dprotaso dprotaso mentioned this issue Sep 15, 2023
Closed
@dprotaso
Copy link
Contributor

dprotaso commented Apr 2, 2024

Closing this - we are tracking this in the repo and eventually we'll have tests that run continously - see #621

@dprotaso dprotaso closed this as completed Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@carlisia @dprotaso @ReToCode