Bug: <app>-gateway network policy uses svc port instead of pod port
Testing packages that utilize wrapper - noticed that there was a communication issue between ingress gateway and the pod.
After looking at the network policy - I noted that the template for the gateway network policy uses the port specified in the istio hosts specification used for the virtualservice.
The problem here is that virtualservice uses a service name and port where as the network policy uses a pod/container port. A majority of the time these may be aligned but not always the case.