vn-maxconf-core
vnet-pexip-syslogs-prod
:::
The platform uses a shared VNet to isolate test and production node traffic by subnet while keeping network governance centralized. The syslog collector uses a dedicated VNet because it is a shared logging target rather than a workload that belongs inside either the test or production Pexip subnet.
| VNet | Resource Group | Location | Address Space |
|---|
vn-maxconf-core | rg-shared-resources | canadacentral | 10.200.48.0/22 |
vnet-pexip-syslogs-prod | rg-pexip-syslogs-prod | canadacentral | 10.20.0.0/24 |
| Subnet | CIDR | Environment | Typical Workloads |
|---|
sn-maxconf-prod | 10.200.48.0/24 | Production | vm-node-mgmt-core, vm-node-conf-core |
sn-maxconf-test | 10.200.49.0/24 | Test | vm-node-mgmt-test, vm-node-conf-test |
snet-pexip-syslogs-prod | 10.20.0.0/26 | Shared logging | vm-pexip-syslogs-prod |
- Environment separation is subnet-based within a single VNet.
- The syslog collector VNet peers with
vn-maxconf-core; a return peering is required for log flow.
- NICs and public ingress controls tie back to this network boundary.
- Any subnet expansion should account for Pexip signaling/media port requirements and NSG policy alignment.
