The Avi Load Balancer Controller includes a framework for tracking and enforcing various system-wide limits, based on the size of the Controller instances and other parameters.

Controller Sizing

The Controller sizing is based on meeting the minimum requirements for both vCPU and memory. For instance, a Controller with 6 vCPUs and 32GB RAM will be classified as Small.

For more information on CPU memory usage, see NSX Advanced Load Balancer Controller Sizing topic in the VMware Avi Load BalancerAdministration Guide.

Note:

  • This applies only to on-premises VMware vCenter Cloud deployments with Tanzu, on a single-node Controller.

  • The minimum Controller size supported from 30.2.1 is 6 vCPU, 32 G RAM (Small).

  • All Controller nodes in a cluster must be homogeneous in terms of memory, CPU, and disk configurations. See Cluster Compatibiliy and Upgrade Requirements to know more.

System Limits

This section provides the recommended configuration limits for VMware products. While configuring, ensure that the mentioned limits are maintained.

The following system limits are supported:

  • Number of tenants

  • Number of VSs with RT Analytics

  • Number of VSs with WAF

  • Number of Service Engines

Ensure that you select the correct software version in VMware Configuration Maximum window. If the specific release being deployed is not listed, select the closest release below the version being deployed.

The maximum number of VSs with WAF is 2500 for Large controller flavor

For more information on the limit enforced for various entities, see VMware Configuration Maximums.

Behavior on Upgrade from a Pre-20.1.1 Release

An upgrade from a pre-20.1.1 release, with the object count exceeding the defined limits, is allowed. However, additional creation/ updates for the object will fail with an error.

Example Scenarios:

  • The Controller cluster with 8 vCPU/ 24 GB RAM, and having 200 virtual services, is upgraded from 18.2.9 to 20.1.1. In this case, the upgrade will succeed. However, the creation of an additional (201st) virtual service or updates to the virtual services will fail.

  • The Controller cluster with 8 vCPU/ 24 GB RAM, and having one Virtual Service and one Pool having 2050 servers, is upgraded from 18.2.9 to 20.1.1. In this case, the upgrade will succeed. However, editing of the pool will not be allowed.