IngressBackend not updating for changes on source Pods

[alk-jozog]

Bug description: We've a setup very similar to https://release-v1-2.docs.openservicemesh.io/docs/demos/ingress_k8s_nginx/. It works fine, except that when the ingress-nginx pods change (rollout restart on the Deployment for instance), it seems OSM doesn't notice it (logs are silent) and envoy is not updated, which means all ingress traffic from the new ingress-nginx Pods is then blocked.

Affected area (please mark with X where applicable):

• Install [ ]
• SMI Traffic Access Policy [ ]
• SMI Traffic Specs Policy [ ]
• SMI Traffic Split Policy [ ]
• Permissive Traffic Policy [ ]
• Ingress [X]
• Egress [ ]
• Envoy Control Plane [ ]
• CLI Tool [ ]
• Metrics [ ]
• Certificate Management [ ]
• Sidecar Injection [ ]
• Logging [ ]
• Debugging [ ]
• Tests [ ]
• Demo [ ]
• CI System [ ]

Expected behavior: OSM should watch the IngressBackend's Source Pods and update the allowed Ingress automatically.

Steps to reproduce the bug (as precisely as possible):

1. Setup https://release-v1-2.docs.openservicemesh.io/docs/demos/ingress_k8s_nginx/
2. Everything works fine
3. Trigger a rollout-restart on the ingress-nginx controller Deployment
4. Ingress traffic is blocked

How was OSM installed?: AKS built-in addon

Environment:

• OSM version (use osm version): 1.2.3
• Kubernetes version (use kubectl version): 1.25.6
• Size of cluster (number of worker nodes in the cluster): ~20

[github-actions[bot]]

This issue will be closed due to a long period of inactivity. If you would like this issue to remain open then please comment or update.

[alk-jozog]

Not stale