bug: workloadentry + service stay on incorrect port

[kyessenov]

The following config does not appear to work:

apiVersion: v1
kind: Service
metadata:
  labels:
    asm_resource_type: VM
  name: kuat-xxx-vm
  namespace: xxx-bugbash-vm-3
spec:
  ports:
  - name: http
    port: 8090
    protocol: TCP
    targetPort: 8090
  selector:
    app: kuat-xxx-vm
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}
---
apiVersion: networking.istio.io/v1beta1
kind: WorkloadEntry
metadata:
  name: kuat-xxx-vm
  namespace: xxx-bugbash-vm-3
spec:
  address: xxxxxxx
  labels:
    app: kuat-xxx-vm
  serviceAccount: xxxxx

istioctl pc endpoint shows:

SERVICE_VIP:80                    HEALTHY     OK                outbound|8090||kuat-asm-vm.asm-bugbash-vm-3.svc.cluster.local

Note that port 80 is used instead of the desired 8090.

cc @howardjohn

[kyessenov]

This happens if the original config has 80 and then edited to have 8090