These repositories document two distinct F5 Distributed Cloud patterns:
| Use case | Purpose |
|---|---|
| Multi-Cloud Networking | Advanced Azure/AWS/KVM CE interface binding, registration, BGP/ECMP, TGW Connect, HA, upgrades and lifecycle automation |
| Canada Topology | Canadian traffic path through DNS, Regional Edge advertisement, actual-source authorization and Canadian CE origin discovery |
MCN and Canada own separate infrastructure and Terraform states.
The Canadian traffic path follows a request from tenant-managed DNS to a reserved public allocation, Toronto/Montreal Regional Edges, an explicitly selected country policy, and an origin discovered through Canadian Customer Edges. Anno 69C0 tated API JSON excerpts explain each control for existing F5 Distributed Cloud users.
The demonstrated policy allows COUNTRY_CA and denies other or unknown classifications, with forwarding-header trust disabled. Canadian origin placement, Canadian public advertisement and source-country authorization are independent decisions. Origin infrastructure ingress uses a separate ACL.
Three Azure Customer Edges, two FRR relays, Azure Route Server, an internal load balancer and an origin stage the demonstration in Canada Central. Its node recovery exercise does not establish cross-region redundancy, comprehensive Canadian data residency or legal compliance. Internal diagnostic listeners are separate from public advertisement. Public IPv6 remains unpublished pending equivalent enforcement verification.
The documentation follows Design, Deploy, Verify and Operate. The configuration map and Terraform source retain their existing URLs.
Terraform is supporting implementation reference. Its source is extracted with attribution from
f5-sales-demo/multi-cloud-networking. The Canada application namespace and registration token are separately owned; CE
sites remain in system, and the reserved allocation remains platform-owned. Independent local Terraform state and backups live outside the Ubuntu checkout in protected storage. Deployment uses the existing Azure CLI login and exclusive deployment/state locks. Credentials belong in private inputs. Shared Marketplace acceptance is a
subscription prerequisite.
See CONTRIBUTING.md for the governed contribution workflow.
See LICENSE.