For a production deployment of VMware Cloud Foundation (VCF), there is a good reason why you might not want to run everything on a single ESX host. 😅
Assuming you understand how the minimum ESX host requirements are derived for VCF deployments, there are certainly benefits to deploying a resource-optimized VCF environment for lab or proof-of-concept (POC) purposes. Being able to exercise workflows such as creating a new VCF Workload Domain or adding a new VCF Cluster with just a single ESX host can be extremely useful.
In fact, this has been possible since VCF 5.x and is something I have personally used to quickly stand up a full VCF environment or expand an existing one, which I have documented over the past few years:
- VCF 5.x Management Domain on single ESX Host (2023)
- VCF 5.x Workload Domain on a single ESX Host (2023)
- VCF 9.0.x Fleet on single ESX Host (2025)
- VCF 9.0.x Workload Domain via VCF Import of single ESX Host (2023)
- VCF 9.1.x Fleet on single ESX Host (2026)
While the scenarios above are the most common use cases for a single ESX host, deploying a new VCF Cluster with just one host has been a less common request, but it has also been possible.
To be able to deploy a new VCF Fleet, Workload Domain or Cluster using just a single ESX host requires applying a workaround, which I have captured in my comprehensive VCF 9.1.x Installer and SDDC Manager Configuration Workaround for Lab Deployments blog post.


