Overview
Provider drivers determine the underlying implementation used to create and manage load balancing appliances. The default provider is configured during XDeploy deployment. You can view available providers, inspect their capabilities, and allow users to select a specific provider at provisioning time.View Available Providers
List available load balancing providers
List provider capabilities
Provider Comparison
| Feature | Amphora | OVN |
|---|---|---|
| Data plane | VM-based appliance | OVN logical flows (no appliance VM) |
| HA topology | ACTIVE_STANDBY supported | Built-in via OVN HA |
| L7 routing | Full L7 policy support | Limited L7 support |
| TLS termination | Supported | Supported |
| Throughput | Limited by appliance VM size | Near line-rate (kernel-based) |
| Appliance overhead | 1 VM per load balancer | No appliance VMs |
| Best for | Full-featured production LBs | High-throughput, simpler LBs |
Configure Default Provider
The default provider is set during XDeploy deployment via globals:XDeploy globals: set default load balancer provider
Deploy load balancer configuration
Specify Provider at Provisioning Time
You can override the default provider when creating a load balancer:Create load balancer with specific provider
Not all providers are available in all deployments. The available providers depend
on which drivers are deployed and configured by the platform administrator.
Next Steps
Flavor Profiles
Create capacity tiers that wrap provider-specific configuration for users.
Architecture
Understand the controller-appliance model for the Amphora provider.
Monitoring
Monitor provider-specific appliance health and statistics.
Admin Troubleshooting
Resolve provider driver configuration and appliance provisioning issues.