refactor: update informer set to use SharedInformerFactory for GKE Networking API and core Kubernetes resources.

[iromanycheva-eng]

Refactor InformerSet to use component SharedInformerFactory instead of handling each Informer individually.
This change is aligned with standard controller idiomatic patterns.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: iromanycheva-eng
Once this PR has been reviewed and has the lgtm label, please assign mmamczur for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS
• pkg/multiproject/OWNERS

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

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: iromanycheva-eng / name: iromanycheva-eng (00e555d, 48cf70e, b8e90ce)

[k8s-ci-robot]

Welcome @iromanycheva-eng!

It looks like this is your first PR to kubernetes/ingress-gce 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/ingress-gce has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @iromanycheva-eng. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[TortillaZHawaii]

/ok-to-test

[iromanycheva-eng]

/cc @swetharepakula , please review the change.

[iromanycheva-eng]

/assign @swetharepakula

[swetharepakula]

for all of the informers we create, set the namespace indexer on them

[swetharepakula]

This change mostly looks good to me.

A couple of comments, to add back the namespace indexer for the informers.

For the commits, can you squash them. If you would like to keep each commit separate, then update the messages to indicate what each commit is doing. Also can you separate out the vendor and the go.mod changes. I would make that the first commit and then have the code changes after that.