-
Notifications
You must be signed in to change notification settings - Fork 30
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
Add TestRetry conformance test #20
Comments
This is going to be pretty tricky for Istio for mesh traffic if the default is not the same as Istio, since we may end up with defaulting to 2 retries, but then if a user defines an HTTPRoute we suddenly switch to no retries. |
This issue is stale because it has been open for 90 days with no |
This issue is stale because it has been open for 90 days with no |
From: kubernetes-sigs/gateway-api#184 (comment) Retries will be controlled by a implementation (ie. istio/contour) specific policy (kubernetes-sigs/gateway-api#713) that attaches to the gateway (or whatever). Details here: https://gateway-api.sigs.k8s.io/references/policy-attachment Thus we won't be able to configure using the GatewayAPI - so we'll still want a test to ensure there are no retries. |
This is a tracking issue for kubernetes-sigs/gateway-api#184.
Currently gateway-apis does not define the API of retry policy. So Istio attempts to retry
503
error which is an Istio's default behavior.We need to wait for gateway-apis defines the API by kubernetes-sigs/gateway-api#184.
The text was updated successfully, but these errors were encountered: