-
Notifications
You must be signed in to change notification settings - Fork 236
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
add regional support to ComputeNetworkEndpointGroup #322
Comments
Hi @flunderpero, currently ConfigConnector only support zonal network endpoint group; I have added the request of regional network endpoint group into our backlog. We will plan and work on it and let you know when we have more information. |
@xiaobaitusi We are also interested in this request. Has there been any update on adding regional support so we can support serverless NEG's through KCC? |
Hello @travisrandolph-bestbuy, no updates yet on this request, but we'll let you know once we have any updates to share. In the meantime, could you elaborate on whether this issue is a blocker, friction point, or nice-to-have for you? |
Related: #502 (asks for both regional and global support for |
@jcanseco Sorry for not replying sooner. This is a friction point for us. Currently we have engineers who need to create the serverless NEG and attach it to our KCC created Load Balancer/URL Map. |
Thanks for the response, @travisrandolph-bestbuy ! |
Closing; supported on KCC 1.87.0 now via https://cloud.google.com/config-connector/docs/reference/resource-docs/compute/computeregionnetworkendpointgroup |
Describe the bug
I am trying to setup a load balancer for our Cloud Run services, but I am unable to create a ComputeNetworkEndpointGroup of type SERVERLESS.
I am able to specify SERVERLESS as
networkEndpointType
butlocation
is expected to be a zone and a SERVERLESS endpoint group requires a region.The error message is either:
... when I try to use a region as
location
, or:Besides that, I don't think there is a way to specify things like
cloud-run-url-mask
, so my attempt to create a proper endpoint group would be futile anyway. :-)ConfigConnector Version
1.29.0
To Reproduce
Steps to reproduce the behavior:
YAML snippets:
The text was updated successfully, but these errors were encountered: