-
Notifications
You must be signed in to change notification settings - Fork 4.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
Feature Request: Application Gateway Backend Pool in VMSS #857
Comments
Hey @squiggleuk Thanks for opening this issue :) Taking a quick look into this - it appears there's a separate block available in ARM Templates and the API which is required to connect an Application Gateway attached to the VM Scale Sets. I've verified that support for configuring the Application Gateway backend exists in the Azure SDK - as such we should be able to implement this in the near future. Thanks! |
+1 for this feature |
Hi @bob2build you could manually build this Pull Request (#884) or alternatively use this CLI / Powershell code (#619 (comment)) to manually attach the App Gateway to the VMSS after it is built Just remember to "upgrade" your VMSS instances afterwards for them to be attached to the App Gateway. |
Thanks @wtfiwtz You are a life saver. |
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 👉 [email protected]. Thanks! |
Terraform Version
Terraform v0.11.3
Affected Resource(s)
azurerm_virtual_machine_scale_set (When used with azurerm_application_gateway)
I'm deploying azurerm_virtual_machine_scale_set with azurerm_application_gateway, but I can't see a way to associate the VMSS nodes, with the backend pool.
It can be done successfully using azurerm_lb...
azurerm_virtual_machine_scale_set.network_profile.ip_configuration.load_balancer_backend_address_pool_ids = ["${azurerm_lb_backend_address_pool.bpepool.id}"]
But if I swap out the backend pool id for one used by azurerm_application_gateway I get the following error:
ag-beap is referencing resource of a wrong type. The Id is expected to reference resources of type loadBalancers/backendAddressPools.
Should there be another attribute under azurerm_virtual_machine_scale_set.network_profile.ip_configuration - Like application_gateway_backend_pools?
...or maybe there is another way to do this that I'm missing?
The text was updated successfully, but these errors were encountered: