📌 Summary

Fix network connectivity issue when a Pod from cluster was trying HTTP request from a local Kubernetes service that is managed by knative service.

Wrong label selector caused that there wasn't any Pod behind the knative-local-gateway k8s service.
This PR ensures that both knative-local-gateway k8s service and knative-local-gateway Istio Gateway are using the correct selector which is istio: ingressgateway-1-26-0-public

🔍 Reviewer Notes

Local service FQDN is mapped to the knative-local-gateway.istio-system.svc.cluster.local
e.g.:

# dig e5-mistral-7b-predictor.team-admin.svc.cluster.local

e5-mistral-7b-predictor.team-admin.svc.cluster.local. 13 IN CNAME knative-local-gateway.istio-system.svc.cluster.local.
knative-local-gateway.istio-system.svc.cluster.local. 13 IN A 10.128.156.142

🧹 Checklist

• Code is readable, maintainable, and robust.
• Unit tests added/updated