Skip to content
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.

Cannot configure backend timeout #226

Open
codefrau opened this issue Jul 31, 2019 · 3 comments
Open

Cannot configure backend timeout #226

codefrau opened this issue Jul 31, 2019 · 3 comments

Comments

@codefrau
Copy link

codefrau commented Jul 31, 2019

We're using kubemci for web socket connections so the default timeout of 30s is way too low.

Our Service has a beta.cloud.google.com/backend-config annotation referencing a BackendConfig that specifies timeoutSec: 3000000.

kubemci appears to ignore the annotation, and instead resets the configured timeout to 30s every time we run it. This causes our customers connections to drop every 30 seconds.

@codefrau
Copy link
Author

Any update on this? kubemci should use the timeout from the BackendConfig, or at least not reset the timeout already configured previously.

Our workaround right now is to run gcloud beta compute backend-services update --timeout=3000000 right after kubemci create --force but updating the load balancer takes a while so there is still a period of time with connections timing out.

@codefrau
Copy link
Author

Workaround suggested by Google Support: recompile with a different default timeout. The line to change is
https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress/blob/master/app/kubemci/pkg/gcp/backendservice/backendservicesyncer.go#L271

@WestonThayer
Copy link

Adding in my use case — I'm using Ingress rules to send traffic to two different services. One is a simple REST HTTP server, so the 30s timeout is fine. But the other is a WebSocket service, so needs a longer timeout.

Setting it manually for now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants