Overview
Provider networks connect tenant virtual networks directly to the physical underlay. Administrators define the physical interface mapping and segmentation type during deployment or reconfiguration. Tenants cannot modify provider network attributes — they select from the options an administrator has made available.Prerequisites
- Admin credentials sourced from
openrc.sh - the deployment console access for cluster-level interface configuration
- Physical network interfaces identified and mapped in the deployment console
Network Type Comparison
Configure Physical Interface Mappings
Provider network parameters are set during initial cluster deployment or reconfiguration via the deployment console. These settings apply to all cluster nodes.- Web Console
Open Networking configuration
In the deployment console, navigate to Configuration → Networking.
Configure physical interface mapping
Set the interface-to-bridge mapping for each network type:
Apply the configuration
Click Save and Deploy. The deployment console applies the settings to all cluster nodes
via ironcore-ansible.
Create Provider Networks
- CLI
Authenticate as admin
Source your credentials file to authenticate with the Polystack platform:
Load credentials
Create a VLAN provider network
Create VLAN provider network
Create a flat provider network
Create flat provider network
--external to mark the network as a valid target for router external gateways.Create a VXLAN network
Create VXLAN tenant network
--share to scope
the network to a specific project.Provider Network Administration
List Provider Networks
List all networks with provider attributes
Update a Provider Network
Update provider network description
Delete a Provider Network
Delete provider network
Segmentation Reference
VXLAN tenant networks are the default type in Polystack deployments. They require no
switch configuration and scale to tens of thousands of isolated tenant networks.
VLAN is recommended when direct integration with physical data center switching is required.
Next Steps
Network Agent Management
Verify L2 agents are healthy on all compute nodes after changing bridge mappings
L3 Router Configuration
Configure routers to use the provider networks you just created as external gateways
Service Architecture
Understand how L2 agents program provider network attachments
Admin Troubleshooting
Resolve VXLAN tunnel and provider network connectivity issues
