-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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.
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
RevisionSpec is missing timeoutSeconds #457
Comments
ela-queue is something we want to retire ideally and just rely on Envoy doing all proxying for us. Might be a good idea to try and implement this in istio if possible. |
Whoever works on this please ping me re. adding this to the conformance tests :D |
dup #487 |
/assign @k4leung4 |
@mattmoor: GitHub didn't allow me to assign the following users: k4leung4. Note that only knative members and repo collaborators can be assigned. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign |
dup #2201 |
re: issue: knative#457 Set default timeout to 60 seconds. Will implement the enforcement of the timeout in future PR.
re: issue: knative#457 Set default timeout to 60 seconds. Will implement the enforcement of the timeout in future PR.
re: issue: knative#457 Set default timeout to 60 seconds. Will implement the enforcement of the timeout in future PR.
re: issue: knative#457 Set revisionspec default timeout to 60 seconds. Add max timeout for cluster ingress at 300 seconds. Add checks that cluster ingress timeout and revisionspec timeout does not exceed cluster ingress max timeout. Will implement the enforcement of the timeout in future PR.
re: issue: knative#457 Set revisionspec default timeout to 60 seconds. Add max timeout for cluster ingress at 300 seconds. Add checks that cluster ingress timeout and revisionspec timeout does not exceed cluster ingress max timeout. Will implement the enforcement of the timeout in future PR.
re: issue: knative#457 Set revisionspec default timeout to 60 seconds. Add max timeout for cluster ingress at 300 seconds. Add checks that cluster ingress timeout and revisionspec timeout does not exceed cluster ingress max timeout. Will implement the enforcement of the timeout in future PR.
re: issue: knative#457 Use ClusterIngress default timeout as max timeout for revisionspec. Add checks that cluster ingress timeout and revisionspec timeout does not exceed cluster ingress default timeout. Will implement the enforcement of the timeout in future PR.
re: issue: knative#457 Use ClusterIngress default timeout as max timeout for revisionspec. Add checks that cluster ingress timeout and revisionspec timeout does not exceed cluster ingress default timeout. Will implement the enforcement of the timeout in future PR.
* Add timeoutSeconds to RevisionSpec re: issue: #457 Use ClusterIngress default timeout as max timeout for revisionspec. Add checks that cluster ingress timeout and revisionspec timeout does not exceed cluster ingress default timeout. Will implement the enforcement of the timeout in future PR. * Pulling in a new knative/pkg to pick up ErrOutOfBoundsValue helper
Pass RevisionTimeoutSeconds down to queue-proxy and have it timeout requests basd on RevisionTimeoutSeconds. knative#457 Add conformance test to ensure request timeouts are handled. knative#1818
Pass RevisionTimeoutSeconds down to queue-proxy and have it timeout requests basd on RevisionTimeoutSeconds. knative#457 Add conformance test to ensure request timeouts are handled. knative#1818
Pass RevisionTimeoutSeconds down to queue-proxy and have it timeout requests basd on RevisionTimeoutSeconds. knative#457 Add conformance test to ensure request timeouts are handled. knative#1818
Pass RevisionTimeoutSeconds down to queue-proxy and have it timeout requests basd on RevisionTimeoutSeconds. knative#457 Add conformance test to ensure request timeouts are handled. knative#1818
From: #444
This field is missing here. I suspect we need something in the request path (e.g.
ela-queue
) that can enforce this.@josephburnett @mdemirhan WDYT?
cc @cooperneil @bobcatfish
The text was updated successfully, but these errors were encountered: