Terminating gateway: Unable to override default 15s http timeout
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 30.1k
- Forks
- 4.6k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 39
Description
#### Overview of the Issue
I have a service in the mesh, that is making requests to an external service outside the mesh.
The external service is registered as a "real" consul service in the catalog, not just through a service-defaults destination.
The calls are going via the terminating gateway, which is set up with custom certificate for the onward connection.
All works fine until http responses take more than 15s to return - at this point I receive 504 timeout errors.
I have tried setting the http timeout by adding a service-defaults entry for the service with LocalRequestTimeoutMs set but this had no effect.
Because the external service needs a "special" certificate, I can't easily switch to tcp either.
Is it possible to set the timeout, and if so, where can I do it?
### Consul info for both Client and Server
Consul 1.17.1 - via helm chart
EKS 1.28
Transparent proxy enabled
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the terminating gateway configuration and the service-defaults entry using LocalRequestTimeoutMs. Reproduce the behavior with an external service response taking more than 15 seconds, then determine whether the timeout can be configured for this gateway path and document the applicable setting or limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, helm, kubernetes
- Domain
- cloud, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100