This section explains the system requirements, software version compatibility, and the network considerations required for installing the cloud. What to read next System RequirementsThis section explains the system requirements of various clouds. Hardware RequirementsThe Avi Load Balancer runs on standard x86-based servers, with no requirement for special-purpose hardware. In general, adding hardware capacity will greatly expand overall system capacity, for both the SEs and Controllers. It is advisable to consult an Avi Load Balancer sales engineer or technical support for recommendations tailored to meet the specific needs of your applications and environment. Software Version CompatibilityThis section gives details on software compatibility versions for various ecosystems. System LimitsThe 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. Proxy Support for Cloud Deployment with Avi Load BalancerWhen Avi Load Balancer is used to provide load balancing to applications residing in public cloud, the Avi Load Balancer Controller communicates with the public cloud provider’s API endpoints for configuration and ongoing operations. Avi Load Balancer IPAM and DNSThis section discusses the native IPAM and DNS support for the various clouds. Networking ConsiderationsAvi Load Balancer Service Engine data interfaces can be assigned to multiple VRFs (Virtual Routing and Forwarding Context). Virtual Routing Framework, or VRF, is a method of isolating traffic within a system. This is also referred to as a 'route domain' within the load balancer community. Changing Avi Load Balancer Controller Cluster ConfigurationThis section describes how to change node membership or node IP address in a Controller Cluster. Avi Load Balancer Controller SizingThis section explains the system capacity of the Controller. Avi Load Balancer Performance DatasheetThis section provides general information about the data path performance of Avi Load Balancer for NSX-T cloud and vCenter cloud. Data Plane Development Kit (DPDK)This section describes about DPDK libraries to provide high-packet performance. Post-installation ConfigurationThis section describes the post-installation process. Memory Upgrade for a Bare Metal DeploymentIf you have under-allocated your machine, the processes get stopped due to high memory consumption. In such a case, you must increase the memory allocated to the Container. This section explains the steps to allocate more memory to the virtual machine hosting the Controller. Tenant SettingsA tenant is an isolated instance of Avi Load Balancer. Each Avi Load Balancer user account is associated with one or more tenants. Adding Custom Tags Using CLI for GCP, Azure and AWSCustom tags are supported for GCP, Azure and AWS cloud. These tags are useful in grouping and managing resources for easier management.