-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
google_compute_backend_service doesn't support serverless NEGs #6876
Comments
@andyroyle can you see if google_compute_region_backend_service works for you? If not, can you post your debug log? |
I'm able to reproduce the same issue. Terraform Versionterraform: 0.13.0 Affected Resource(s)
Terraform Configuration Files
Expected BehaviorBackend should be created. Actual Behavior
|
backend-service-serverless-neg-error.txt |
@kentb does google_compute_region_backend_service work for you? |
@edwardmedia |
If it helps, here are the details of a Backend Service I created using gcloud commands, connected to 2 Serverless NEGs in us-east4 and europe-west1. (Names are swapped w/ more generic ones)
|
@andyroyle v3.35.0 has just released today which contains below feature. Let me know if that helps address your issue. Thanks
https://github.com/hashicorp/terraform-provider-google/blob/master/CHANGELOG.md |
@edwardmedia I don't believe this helps - unless I'm missing something. That release allows you to create the serverless NEG resource. However, you still cant reference that resource within the google_compute_backend_service since its not "serverless neg aware" and tries to apply max utilisation to the resource. :) |
I filed #7051 as I ran into the point that @robcharlwood points out. |
@slevenick By removing the
|
closing this issue as #7051 for tracking this issue |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
terraform: 0.12.28
google-beta: 3.32.0
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
Backend should be created.
Actual Behavior
The api doesn't allow specifying
maxUtilization
for a serverless NEG backend, there is code for explicitly supporting global NEGs (see here) but it's specifically looking forglobal/networkEndpointGroups
in the string, so the serverless NEGs don't trigger this behaviour.Since the Serverless NEGs are now in Beta I thought it prudent to open an issue (in case the fix for this is already in the pipeline).
I can easily send a PR to fix this logic so that it also applies to regional NEGs but I'm not sure of the wider implication here and wouldn't want to break any other behaviour.
The text was updated successfully, but these errors were encountered: