-
Notifications
You must be signed in to change notification settings - Fork 369
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
Not able to change Timeout configuration and values. #1509
Comments
hey @saurabh-tiket EnvoyPatchPolicy is still WIP and will be part of v0.5.0. |
Hey @arkodg Thanks for the quick reply! It's great to know that EnvoyPatchPolicy is still cooking and will be served in v0.5.0. Definitely looking forward to being able to tinker with the route timeout to the backend. Issue #1492 does look related, I'll be keeping an eye on both these threads. By the way, do you have any rough timeline on when v0.5.0 might drop? Just trying to plan things out on my end. Cheers |
@saurabh-tiket this milestone link should have more details. |
@arkodg Ok thanks |
blocked on https://gateway-api.sigs.k8s.io/geps/gep-1742/ moving into |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
closing in favor of #877 |
We are evaluating Envoy as our API gateway, During our POC we realized one of our backends was taking some time to produce a response (more than 15 seconds) and the envoy proxy giving an
upstream timeout
error.While trying to change this value during manifests, I realized it is not possible. I checked the
Policy Attachment
documentation and realised there is no way to change this value. this is the value I need to changehttps://www.envoyproxy.io/docs/envoy/latest/api-v3/config/route/v3/route_components.proto#envoy-v3-api-field-config-route-v3-routeaction-timeout
Can someone confirm whether it is possible to change this value? I also see a similar issue here #1169
I tried reading the SPEC of
EnvoyPatchPolicy
CRD and I think it is not supportedI tested with the following manifest to apply
EnvoyPatchPolicy
, (this is not the correct manifest and needs an update)Also, I tried applying a test
EnvoyPatchPolicy
and wasn't able to succeed. I think the documentation on how to useEnvoyPatchPolicy
is not clear.The example I used is https://github.com/envoyproxy/gateway/blob/1907687b3c76d72073310e54333226bcb3bee96e/docs/latest/design/envoy-patch-policy.md
Following is the error I'm getting
Can someone help us to confirm whether it is possible to change this timeout value ?? It is a blocker for us to use envoy in production.
The text was updated successfully, but these errors were encountered: