Use Informer Cache For NSX-Operator and VM-Operator

[DanielXiao]

What would you like to be added?

I propose to use client-go Informer cache to get and list objects of nsx-operator and vm-operator.

Why is this needed?

Currently the client's get/list call kube-apiserver directly which increase its load and may have performance issues in a large scale WCP environment. Controller-runtime by default add the resource's informer cache at the first time get/list is called.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale