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
Similar to previous issue, #1400
Consul CRD serviceDefauts seems miss configuration LocalConnectTimeoutMsLocalRequestTimeoutMs which is available to use on hcl type config.
Feature Description
Consul service-defaults config entry supports setting LocalConnectTimeoutMs and LocalRequestTimeoutMs
This feature is supported in consul agent binary and hcl config, but not in k8s crd
Use Case(s)
The user needs to config timeout for upstream connection, otherwise, the defaults value for LocalRequestTimeoutMs (15s) might be too short for some long-running request
Seems the changes required are very similar to PR: #1437
So, I basically take it as reference, and add two fields "LocalConnectTimeoutMs" and "LocalRequestTimeoutMs" in a similar fashion, please take a look.
Similar to previous issue, #1400
Consul CRD serviceDefauts seems miss configuration
LocalConnectTimeoutMs
LocalRequestTimeoutMs
which is available to use onhcl
type config.Feature Description
Consul service-defaults config entry supports setting LocalConnectTimeoutMs and LocalRequestTimeoutMs
This feature is supported in consul agent binary and
hcl
config, but not in k8s crdUse Case(s)
The user needs to config timeout for upstream connection, otherwise, the defaults value for LocalRequestTimeoutMs (15s) might be too short for some long-running request
cc @david-yu @thisisnotashwin @t-eckert
(Since I saw your guys made the contribution on PR #1437)
Seems the changes required are very similar to PR: #1437
So, I basically take it as reference, and add two fields "LocalConnectTimeoutMs" and "LocalRequestTimeoutMs" in a similar fashion, please take a look.
🤖🤖🤖🤖🤖🤖🤖🤖🤖🤖🤖🤖🤖🤖
PR link:
#1647
🤖🤖🤖🤖🤖🤖🤖🤖🤖🤖🤖🤖🤖🤖
The text was updated successfully, but these errors were encountered: