Open JeffGiroux opened 2 years ago
Thanks for requesting this enhancement. Its been added to our backlog and is now being tracked with internal ID, ESECLDTPLT-3138.
Is this going to make the next release (zone selection per BIG-IP VM instance)? If not, what is estimated time? Tnhx
Is your feature request related to a problem?
Yes, BIG-IPs are deployed to same availability zone and this reduces physical redundancy.
Describe the solution you'd like
User would like to deploy BIG-IP to two different availability zones. This will require an additional zone parameter where the 2nd BIG-IP will be deployed to the second zone.
Describe alternatives you've considered
Right now in current template form, user must edit the python script file to adjust for a second zone and/or modify the yaml file to pass an additional zone parameter into python file...both requiring edits.
Additional context
BIG-IP deployment should follow cloud best practices and CSP recommended guidance for SLAs and HA. This results in BIG-IP needing to be deployed to multiple AZs.