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
{{ message }}
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 aBackendConfig
that specifiestimeoutSec: 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.The text was updated successfully, but these errors were encountered: