Azure / Azure/Azure-Landing-Zones
Support Azure Route server for multi-region failover and routing
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 97
- Forks
- 70
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 7
Description
Good afternoon
We currently have on-prem VPN connectivity from uksouth/ukwest firewalls and the on-prem team are proposing handling HA at their end via BGP to Azure vnet gateway. However, in addition to that, we want to re-route traffic from spoke vnets via the alternative firewall should one become unavailable somehow. I'm pretty sure we need route server for this (as opposed to automating the rewriting of UDRs somehow). Any plans for this to be supported in alz-bicep ? We can do it via bicep ourselves, but a best-practice deployment via alz-bicep would be useful.
Why is this feature important. Describe why this would be important for your organization and others. Would this impact similar orgs in the same way?
To allow easier management of azure route table maintenance, as published by BGP.
Please provide the correlation id associated with your error or bug.
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Can you describe any alternatives that you have taken since this feature does not exist?
Automation with network watching probes and rewriting of UDRs. Not ideal.
Feature Implementation
Check previous GitHub issues
- I have searched the issues for this item and found no duplicate
Code of Conduct
- I agree to follow this project's Code of Conduct
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Azure Route Server requirements and the alz-bicep support requested in this issue. Compare the proposed best-practice deployment with the stated alternative of monitoring probes and rewriting UDRs. Done means the supported scope, affected deployment configuration, and validation approach are defined and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100