Trigger NEG syncers to sync on Node Topology CRD changes.

[sawsa307]

/assign @swetharepakula
/assign @gauravkghildiyal

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sawsa307
Once this PR has been reviewed and has the lgtm label, please ask for approval from gauravkghildiyal. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sawsa307]

/retest

[gauravkghildiyal]

Have left a few comments and have one additional one:

Have we considered starting a filtered informer for NodeTopology which only informs changes to a specific resource? You can make the name of that resource pluggable through a flag to get some flexibility.

I can see why choosing the option of having an un-filtered informer might offer more flexibility for future use cases, where things might work naturally if you ever have multiple NodeTopology resources. But on the other hand, I also feel that if such a case actually arises, it would warrant some additional thought and verification (like maybe not syncing all syncers for each NodeTopology resource? or something like that)

This specific aspect may benefit from getting an additional opinion (@swetharepakula)

[sawsa307]

Have we considered starting a filtered informer for NodeTopology which only informs changes to a specific resource? You can make the name of that resource pluggable through a flag to get some flexibility.

Discussed offline, and created #2694. We only care about update on the CR named default.