WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
    • VMware Cloud Foundation 9
  • VKS
  • Homelab
    • Hardware Options
    • Hardware Reviews
    • Lab Deployment Scripts
    • Nested Virtualization
    • Homelab Podcasts
  • VMware Nostalgia
  • Apple
You are here: Home / VMware Cloud Foundation / Single Node VMware Avi Load Balancer with VCF 9.0

Single Node VMware Avi Load Balancer with VCF 9.0

07.22.2025 by William Lam // 9 Comments

VMware Cloud Foundation (VCF) 9.0 continues to support one of the most popular and powerful load balancer, VMware Avi Load Balancer. When you deploy a new VMware Avi Load Balancer within a given VCF Domain, by default SDDC Manager will deploy three VMware Avi Controllers for high availability purposes.

For lab purposes, you may not need all three VMware Avi Controllers but there was no way to change the system default in earlier releases of VCF. With VCF 9.0, we now have way to deploy just a single VMware Avi Controller, which is fantastic for lab and testing purposes.

Disclaimer: This is not officially supported by Broadcom, use only within a lab environment.

Step 1 - Download your desired version of the VMware Avi Load Balancer OVA (e.g. controller-31.1.1-9122.ova) from the Broadcom Support Portal.

Step 2 - Upload the VMware Avi OVA to SDDC Manager to make it aware of the Avi Bundle. Please refer to the Broadcom documentation HERE that provides a nice script that will upload the VMware Avi OVA along with the required Product Version Catalog and Signature file, which you will also need to download.

Step 3 - SSH to SDDC Manager and add the following configuration to /home/vcf/feature.properties

feature.vcf.vgl-41078.alb.single.node.cluster=true

We now need to restart the SDDC Manager services by running the following command:

echo 'y' | /opt/vmware/vcf/operationsmanager/scripts/cli/sddcmanager_restart_services.sh

Step 4 - Use the deploy_one_node_nsx_alb.ps1 PowerShell script to deploy the single VMware Avi Controller as the SDDC Manager UI has hardcoded the three controller requirement, make sure to update the script with your own configuration before running as shown in the screenshot below:


You can monitor the progress of the VMware Avi deployment by using the SDDC Manager UI


As you can see from the screenshot below, our VMware Avi cluster is just a single node versus the three that is deployed by default!

Categories // VMware Cloud Foundation Tags // AVI, NSX Advanced Load Balancer, VCF 9.0

Comments

  1. *protectedViktor Balogh says

    07/22/2025 at 8:55 am

    now that is a really cool feature! 👏

    Reply
    • *protectedjerry says

      10/31/2025 at 3:06 am

      I would like to inquire about replacing the NSX Load Balancer with AVI in a VPC within VMware Cloud Foundation. Could you please advise on the recommended approach, or provide any SOPs or reference documentation for this process?

      thank you 🙂

      Reply
      • William Lam says

        10/31/2025 at 6:56 am

        Please see https://techdocs.broadcom.com/us/en/vmware-security-load-balancing/avi-load-balancer/avi-load-balancer-vmware-cloud-foundation/9-0/deploying-avi-load-balancer-in-vcf.html

        Reply
  2. *protectedMH says

    07/24/2025 at 2:43 pm

    Is there documentation for how to build clusters within a supervisor namespace that is on NSX VPCs + Avi Load balancers? I'm struggling to find how to construct the yaml files for a test cluster, before we rework them for a helm chart, and I'm seeing an error similar to "virtualmachine service lb does not have vip assigned virtual machine service does not have ingresses"

    Reply
    • *protectedlukasztworek says

      07/26/2025 at 1:52 pm

      have same issue

      Reply
    • William Lam says

      07/26/2025 at 3:40 pm

      When you say build a cluster, are you referring to deploying a vSphere Kubernetes Cluster?

      Reply
      • *protectedMH says

        07/26/2025 at 4:43 pm

        Yes - I think I’m past the error I had before, but now it’s just weird. It’s building the VKS Cluster inside the namespace I made, and I see the services and pools come up in Avi, but then go red after the cluster control plane node comes online. Everything in NSX seems to be provisioned as well with the VPC l.

        It feels like it’s almost there but I’m missing something simple that’s not in the documentation. Not sure if it’s NSX VPC, or Avi, or I need to build the namespace with a custom network or what.

        Reply
        • William Lam says

          07/28/2025 at 10:34 am

          Would you mind if I connected you directly with a couple of experts in this area offline?

          Reply
          • *protectedMH says

            07/29/2025 at 7:30 pm

            I think I’m past it now, working with some folks the TAM got aligned with yesterday and today - thanks though!

            Not sure exact issue because I did a lot of stuff to try to get it fixed - definitely the Avi management segment in NSX not having DHCP addresses contributed though

Thanks for the comment!Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • Automating the Reporting of VCF Workload Domain Import Pre-Check Validations 12/04/2025
  • Import vCenter Server with Single ESX Host as new VCF Workload Domain? 12/03/2025
  • Managing Storage for VCF Automation (VCFA) Content Library Transfer Spooling Area 12/01/2025
  • Enabling new vSphere Kubernetes Service (VKS) Cluster Management for VCF Automation (VCFA) 11/21/2025
  • Realtek Network Driver for ESXi 11/12/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.

To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025

 

Loading Comments...