-
Notifications
You must be signed in to change notification settings - Fork 303
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BackendConfig timeoutSec doesn't seem to work with GCE Ingress #598
Comments
@ConradIrwin Are you running a GKE cluster with version at or above 1.11.3-gke.18? cc @rramkumar1 |
I'm running the default for Google Cloud, which seems to currently be |
As per https://cloud.google.com/kubernetes-engine/docs/how-to/configure-backend-service, you will need to upgrade GKE master version to >= 1.11.3-gke.18 to be able to configure timeoutSec via BackendConfig. |
Ah, thank you, and sorry for the confusion. |
For some reason this is not working as of GKE 1.21 either. |
I am running GKE 1.24 and I too cannot get it to apply for some reason. I even deleted the ingress and created it again with no luck. Here is what I am doing: Backendconfig:
ingress:
|
I made an error, now it works. see #1803 |
Just out of nowhere it started working too here, but, it takes some minutes to reflect the changes, which is an acceptable thing. |
I created a backendconfig object like this:
and attached it to the service like this:
and created an ingress like this:
The load balancer created in my google cloud project correctly had the CDN enabled, but the timeout was still displayed as 30 seconds in the Google Cloud Console. I have since edited the timeout using the Google Cloud Console and it seems to stick with the value of 120 that I set manually.
The text was updated successfully, but these errors were encountered: