Hello,
please note the exact wording, NVDS actually only refers to the old implementation. The new variant is called “VDS” or occasionally “CVDS”. It was used imprecisely in the question...
Francois Tallet has written a very good document on the subject of NVDS/VDS: https://community.broadcom.com/applications-networking-security/blogs/francois-tallet/2024/11/21/moving-from-nvds-to-vds
Although the NVDS provided the same functions as a vCenter VDS, it was fully managed by NSX. It could therefore also be deployed from NSX (outside of vCenter).
If you take a close look at the new construct with VDS and the NSX extensions, almost all functions are provided by the (C)VDS. NSX only adds a few additional features.
This also explains why the VDS must be provided by the vCenter (outside NSX). The NSX transport node profile (vCenter doesn' know anything about it) then only refers to the NSX additional features, and is provided by NSX manager.
The new order is:
1. you create a transport node profile (possibly specific to an ESX cluster)
2. connect the Compute Manager (vCenter) to the NSX Manager
3. the ESX clusters from the Compute Manager become visible in the NSX Manager (Transport Node Collections)
4. you assign a Transport Node Profile to a Transport Node Collection in the NSX Manager
5. all existing hosts in the ESX cluster automatically receive the NSX configuration according to the TNP
If you want to add another host, you just have to move it into the ESX cluster in vCenter...
Kind regards
Hannes