Change to use dynamic client for NSX Operator API #864
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
What would you like to be added?
Change to use dynamic client for NSX Operator API
Why is this needed?
Because we choose to use dynamic client for VM Operator API, it is better to align NSX Operator API with it.
The text was updated successfully, but these errors were encountered: