After standing up a fresh VCFA 9.0 instance I'm navigating the initial configuration and am trying to understand the initial configuration paths. When I first login to VCFA I'm greeted with the "Prerequisites for setup are missing" with the options "ENABLE SUPERVISOR IN OPS" and "CONTINUE TO VCF AUTOMATION". As I read the documentation [REF1, REF2] it seems that implementing vSphere Supervisor is a requirement. This implies using the newer kubernetes method for provisioning and management of virtual machines. If I look at the upgrade documentation [REF3] there is no mention of vSphere Supervisor.
REF1: "Overview of VCF Automation Provider Management" (https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-0/provider-management/overview-of-vcloud-director-administration.html)
REF2: "Quick Start Your VCF Automation Setup" (https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-0/provider-management/getting-started-with-the-vcloud-director-service-provider-portal/quick-start-your-vcf-automation-setup.html)
REF3: "Upgrade VMware Aria Automation to VCF Automation 9.0" (https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-0/deployment/upgrading-cloud-foundation/preparing-your-vcf-9-management-components/phase-3-import-and-upgrade-aria-automation-8-to-vcf-automation-9/upgrade-to-vcf-automation.html)
Q1: Am I correct that vSphere Supervisor, and by extension kubernetes, is a hard requirement for greenfield deployment of VCFA 9.0?
Q2: If upgrading from Aria Automation 8.x to VCFA 9.0 is there some point where vSphere Supervisor, and by extension kubernetes, becomes a hard requirement?
-------------------------------------------