jtracey93
commented
7 months ago Thanks for logging @terrymandin
For this issue we will focus on the ALZ Bicep & TF accelerators (https://aka.ms/alz/accelerator/blog) and how we need to enhance, adjust and guide customers on how to handle their CI/CD setups to handle a regional/zonal outage.
However, we will not focus on the ALZ services and architecture itself, as @brsteph is working on this already as part of AB#30480 and @sebaseem has already looked at ALZ from a zonal redunadncy perspective under AB#27344 and we have stories to make some small changes as part of that feature too.
Let me know if that makes sense and you agree or not and then myself @oZakari, @matt-FFFFFF, @jaredfholgate & @luke-taylor can get together and discuss this further with the lens of the CI/CD accelerators and their tightly coupled resources (state file storage etc.)
oZakari
jaredfholgate
Description
We are directing our customers to build more resilient Azure deployments. See: Recommendations for using availability zones and regions.
The Accelerator Azure architecture should provide built in zone resiliency and provide options for regional resiliency. Customers should also be aware of GitHub and Azure DevOps resiliency options.
Customers should be able to deploy if there is a zone outage, and if they have selected regional resiliency, know that they can still deploy if there is a regional outage.
Describe the solution you'd like
Describe any alternatives you've considered
Additional context