Long story short, I had to open the C# client to find out what 'warning/error' it was complaining about. Quite simply, I had forgotten to re-add the hosts back into the vDS and migrate the vMotion/vSAN vmk connections.
Man-o-man, I see why so many people complain about the web client.
The upside to the story was I found out a couple of things about vSAN.
- Having a 3-node cluster minimum, I was able to remove and re-add each host back into the cluster with no issues to VM's running on each host.
- Even w/ the vDS problem, vSAN kept chugging along w/ VM's running just fine.
- In other words, even without vCenter managing things, the ESXi hosts kept everything running just fine.
- This was on my mac mini vSAN cluster.