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
I have an ingress gateway with a WASM plugin (envoy filter) installed which runs of every request.
I'm experiencing 503 response code intermittently with response_code_details as http2.remote_reset on our ingress gateway. The response_flags, route_name, upstream_host and upstream_local_address comes as null which might indicate a discovery related issue. The value for duration comes as quite high (~10K-30K). It seems that the request doesn't reach the destination service as I also don't see any proxy logs on the destination service sidecar.
The issue gets resolved for some time after I delete and reapply the WASM plugin. I again start facing the issue after some days (sometimes weeks, happens intermittently). Could this be caused due to WASM or something else related to discovery?
Any idea on why this could be happening or how to troubleshoot the issue?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I have an ingress gateway with a WASM plugin (envoy filter) installed which runs of every request.
I'm experiencing 503 response code intermittently with response_code_details as http2.remote_reset on our ingress gateway. The response_flags, route_name, upstream_host and upstream_local_address comes as null which might indicate a discovery related issue. The value for duration comes as quite high (~10K-30K). It seems that the request doesn't reach the destination service as I also don't see any proxy logs on the destination service sidecar.
The issue gets resolved for some time after I delete and reapply the WASM plugin. I again start facing the issue after some days (sometimes weeks, happens intermittently). Could this be caused due to WASM or something else related to discovery?
Any idea on why this could be happening or how to troubleshoot the issue?
Thanks for the help.
Beta Was this translation helpful? Give feedback.
All reactions