Potential to trigger ConfigMapReconciler less on MeshGateway changes

[lobkovilya]

What happened?

1. Kuma CP enqueues events for all MeshGateways even though we can do this only for MeshGateways with crossMesh listeners

   kuma/pkg/plugins/runtime/k8s/controllers/configmap_controller.go

   Line 157 in beb3c36

   func MeshGatewayToMeshMapper(client kube_client.Reader, l logr.Logger, ns string, resourceConverter k8s_common.Converter) kube_handler.MapFunc {

2. By looking at the algorithm that generates VIPs it seems like we don't need to watch MeshGatewayRoutes

   kuma/pkg/plugins/runtime/k8s/controllers/configmap_controller.go

   Line 95 in beb3c36

   Watches(&mesh_k8s.MeshGatewayRoute{}, kube_handler.EnqueueRequestsFromMapFunc(MeshGatewayRouteToMeshMapper(mgr.GetClient(), r.Log, r.SystemNamespace, r.ResourceConverter))).

[jakubdyszkiewicz]

Triage: @michaelbeaumont to check if need this

[michaelbeaumont]

Yeah I don't think we need MeshGatewayRoute, information from them isn't used in the VIP handling

[github-actions]

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

[github-actions]

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

[github-actions]

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

[github-actions]

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.