You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 14, 2024. It is now read-only.
There are some features like "Retries and Timeouts" for traffic management in other mesh like istio. I didn't find the corresponding features/API in nginx-service-mesh.
May I know if we have such features on the roadmap or any alternative approach to achieve in nginx-service-mesh?
The text was updated successfully, but these errors were encountered:
it looks like they are for different purpose https://istio.io/latest/docs/concepts/traffic-management/#retries ? pls correct me if I'm wrong. The scenario is when there is temporary networking failure and we expect the sidecar proxy can retry for several times behalf of the client app.
It appears that retries is for errors in the path between encrypting sidecars.
I would not expect this to be a problem within a K8s cluster, but rather when the mesh is extended to services outside or between clusters. @Shuanglu can you help us understand your need / use case for this setting?
It appears that retries is for errors in the path between encrypting sidecars. I would not expect this to be a problem within a K8s cluster, but rather when the mesh is extended to services outside or between clusters. @Shuanglu can you help us understand your need / use case for this setting?
Retries and Timeouts have been added to our backlog of work. I will update this ticket when I have more details on when these features will be released.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There are some features like "Retries and Timeouts" for traffic management in other mesh like istio. I didn't find the corresponding features/API in nginx-service-mesh.
May I know if we have such features on the roadmap or any alternative approach to achieve in nginx-service-mesh?
The text was updated successfully, but these errors were encountered: