Skip to content
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

Limitation not reflected in UI when creating load balancer with serverless NEG #108

Open
scr4bble opened this issue Nov 6, 2020 · 0 comments

Comments

@scr4bble
Copy link

scr4bble commented Nov 6, 2020

As I am not really sure where to report this, plese redirect me elsewhere if this is not the right place or please add it to FAQ - I spent quite some time figuring this out.

When cloud run is used in combination with Google Cloud Load Balancer, there is a restriction that timeout has to be 30 seconds. Documented here.

GCLB creation UI:
Despite the limitation being documented (although not easy to find), user web interface for GCLB creation (more specifically backend service creation inside that) forces you tu enter timeout when creating the backend service. Then at the end, when you confirm the creation it fails with misleading error "Timeout sec is not supported...."
I guess it should still show you this field in the UI (if timeout will be enforced), just disabled, as you cannot change it.
It's probably worth to be here, in the FAQ - maybe also referenced in parts that suggests using GCLB in front of Cloud run as solution to something else.

Thank you for this repo btw. It's a great thing to have a place like this although I understand it must be difficult to keep it up to date in such a fast changing environment. It should definitely be supported by Google officially.

@scr4bble scr4bble changed the title Limitation not reflected in UI when creating load balancer Limitation not reflected in UI when creating load balancer with serverless NEG Nov 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant