Work In Progress..
terraform init
terraform apply --auto-approve
Currently, the process of creating BGP connections will encounter a failure because the APIs of the azapi provider are not waiting for the Virtual Hub's routing status to be fully provisioned before they report success. If you experience this failure, a simple workaround is to run terraform apply once more. This should help complete the process successfully.
Github issue: Azure/terraform-provider-azapi#402
kubectl apply -f manifests
kubectl -n calico-system exec -t $(kubectl -n calico-system get po -l k8s-app=calico-node -ojsonpath='{.items[0].metadata.name}') -- birdcl -s /var/run/calico/bird.ctl -r show proto all
kubectl -n calico-system exec -t $(kubectl -n calico-system get po -l k8s-app=calico-node -ojsonpath='{.items[1].metadata.name}') -- birdcl -s /var/run/calico/bird.ctl -r show proto all
RT=$(az network vhub route-table show --resource-group demo-virtual-wan --vhub-name demo-virtual-wan-vhub --name defaultRouteTable --query id -o tsv)
az network vhub get-effective-routes -g demo-virtual-wan -n demo-virtual-wan-vhub --resource-type RouteTable --resource-id $RT
terraform destroy --auto-approve
or
az group delete --resource-group <RESOURCE GROUP> --no-wait
- Microsoft Virtual WAN documentation - Configure BGP peering to an NVA
- Microsoft Virtual WAN documentation - Configure Azure Firewall in a Virtual WAN hub
- Microsoft Virtual WAN documentation - Virtual WAN routing deep dive
- Microsoft Build 2023 - You really can manage ALL Microsoft Azure services and features with Terraform
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent