Skip to main content

Overview

Flavor profiles define the compute capacity and topology configuration allocated to load balancing appliances. Administrators create named flavors that users select at load balancer provisioning time. Flavors abstract provider-specific settings into human-readable capacity tiers — e.g., standard, ha, and high-performance.
Administrator Access Required — This operation requires the admin role. Contact your Polystack administrator if you do not have sufficient permissions.

Flavor Architecture

A flavor profile is always associated with a specific provider. Multiple flavors can reference the same profile.

Create a Flavor Profile

Create a flavor profile

A flavor profile wraps provider-specific settings:
Create standard single-topology profile
Create HA active-standby profile

Create named flavors for users

Expose profiles as named flavors:
Create standard flavor
Create HA flavor

Verify flavors are available

List available flavors
Flavors appear in the list with status enabled — you can now select them when creating a load balancer.

Flavor Profile Settings Reference


Manage Flavors

Disabling a flavor prevents new load balancers from using it but does not affect existing load balancers. Deleting a flavor profile that is referenced by a flavor will fail — delete the flavor first.

For most production deployments, provide at least two flavors:

Next Steps

Provider Drivers

Understand provider-specific flavor profile settings.

Quotas

Control how many load balancers projects can provision across all flavors.

Architecture

Understand how appliance topology affects data plane resilience.

Admin Troubleshooting

Diagnose flavor-related provisioning failures.