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

There is no mention to dynamic resources as one VMSS #26233

Open
otero16 opened this issue Oct 8, 2024 · 2 comments
Open

There is no mention to dynamic resources as one VMSS #26233

otero16 opened this issue Oct 8, 2024 · 2 comments
Assignees
Labels
Compute - VMSS customer-reported question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.

Comments

@otero16
Copy link

otero16 commented Oct 8, 2024

Type of issue

Missing information

Feedback

We have dynamic elements such as one VMSS that can scale up or down, i am looking for a way to add this resource as the backend pool for one appgw, however using static ip addresses or fqdn is not working, when i scale my vmss the app gw is not capable of pointing to the new instances as the IP addresses have changed. Can you please explain how can we add one dynamic VMSS as the backend for AppGw??

Page URL

https://learn.microsoft.com/en-us/powershell/module/az.network/add-azapplicationgatewaybackendaddresspool?view=azps-12.4.0&viewFallbackFrom=azps-12.2.0

Content source URL

https://github.com/Azure/azure-powershell/blob/main/src/Network/Network/help/Add-AzApplicationGatewayBackendAddressPool.md

Author

@mikefrobbins

Document Id

9c13c173-3db9-d11f-b9de-c45d4d1431dc

@otero16 otero16 added the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Oct 8, 2024
@isra-fel isra-fel added Compute - VMSS Service Attention This issue is responsible by Azure service team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that and removed needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Oct 10, 2024
Copy link
Contributor

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @TravisCragg-MSFT, @sandeepraichura.

@fitzgeraldsteele
Copy link

Agreed, adding instances individually would be a pain. Instead, I would update the scale set virtualMachineProfile.networkProfile to add the backendpool of the AppGw in the model. In powershell, that looks something like:

# Find the backend address pool in the application gateway
$backendAddressPool = $appGw.BackendAddressPools | Where-Object { $_.Name -eq $backendAddressPoolName }

# Add the backend address pool to the VMSS
$vmss.VirtualMachineProfile.NetworkProfile.NetworkInterfaceConfigurations[0].IpConfigurations[0].ApplicationGatewayBackendAddressPools += $backendAddressPool

# : Update the VMSS
Update-AzVmss -ResourceGroupName $resourceGroupName -Name $vmssName -VirtualMachineScaleSet $vmss

So that updates the scale set model. Any new instances will be added to the AppGw backend pool. Existing instances will be updated depending on the upgrade policy: https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-upgrade-policy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Compute - VMSS customer-reported question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

4 participants