contour: Unable to change connect_timeout in Envoy config
What steps did you take and what happened: Running into the Envoy issue reported here
Based on this comment, I’d like to update the connect_timeout setting in the envoy.json config file. However, due to the way Contour bootstraps Envoy, this isn’t easily configurable.
There is another issue open pertaining to Envoy defaults here that would have the default increased to 15 seconds from 250ms.
There’s also another issue pertaining to the configurability of these knobs here.
Environment:
- Contour version: 1.1.0
- Kubernetes version: (use
kubectl version): 1.17.2 - Kubernetes installer & version: kubeadm
- Cloud provider or hardware configuration: GCP
- OS (e.g. from
/etc/os-release): Ubuntu 18.04
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 39 (27 by maintainers)
Commits related to this issue
- internal/envoy: change the upstream connect timeout Change the Envoy connect_timeout from 250 msec to 2 seconds for upstream clusters. Updates #2264 Signed-off-by: Tero Saarni <tero.saarni@est.tech... — committed to Nordix/contour by tsaarni 3 years ago
- internal/envoy: increase default upstream connect timeout This change sets the new default connect timeout to 2 seconds. The default connect timeout was 250 msec which can be too short and may cause ... — committed to Nordix/contour by tsaarni 3 years ago
- internal/envoy: increase default upstream connect timeout (#4151) This change sets the new default connect timeout to 2 seconds. The default connect timeout was 250 msec which can be too short and ... — committed to projectcontour/contour by tsaarni 3 years ago
- internal/envoy: increase default upstream connect timeout (#4151) This change sets the new default connect timeout to 2 seconds. The default connect timeout was 250 msec which can be too short and ma... — committed to Nordix/contour by tsaarni 3 years ago
Configuring the connect timeout sounds totally reasonable to me.
There’s 2 places:
TimeoutPolicy@michmike yes, they’re running into a scenario where the handshake appears to be taking longer than the current timeout. it fails every time.