- |
  **Fixed** an issue causing traffic to match an unexpected route when using wildcard domain names and including an port in the `Host` header.
- |

# If port is unnamed or port name doesn't follow <protocol>[-<suffix>], the analyzer will report warning.
apiVersion: v1
kind: Service
metadata:
  name: my-service
  namespace: my-namespace
spec:
  selector:
    app: my-service
  ports:
  - name: tcp-foo
    protocol: TCP
    port: 8080
    targetPort: 8080
---
# internal waypoint, should not generate warning
apiVersion: v1
kind: Service
metadata:
  labels:

apiVersion: gateway.networking.k8s.io/v1beta1
kind: Gateway
metadata:
  name: invalid-listener-port
spec:
  gatewayClassName: acme-lb
  listeners:
  - name: foo
    protocol: HTTP

  **Fixed** a bug when a Sidecar is resource is defined with multiple egress listeners with different ports 
  of a Kubernetes service, does not merge the ports correctly. This leads to creating only one Cluster with 

apiVersion: gateway.networking.k8s.io/v1beta1
kind: HTTPRoute
metadata:
  name: invalid-backend-port
spec:
  rules:
  - backendRefs:
    - name: my-service1

apiVersion: release-notes/v2
kind: feature
area: istioctl
releaseNotes:
  - |

apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: db-tls
spec:
  host: mydbserver.prod.svc.cluster.local
  trafficPolicy:
    portLevelSettings:
      - port:
          number: 443
        tls:
          mode: SIMPLE

dwq <******@****.***> 1711400865 +0800

Akshay J Nambiar <******@****.***> 1683529381 +0530

apiVersion: security.istio.io/v1beta1
kind: PeerAuthentication
metadata:
  name: "per-port"
  annotations:
    test-suite: "beta-per-port-mtls"
spec:
  selector:
    matchLabels:
      app: b
  mtls:
    mode: DISABLE
  portLevelMtls:
    # 8090 is the targetPort for service http(80)
    8090:
      mode: STRICT
---
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: "default"