[Gateway API] Multiple TLS Passthrough listeners with the same Hostname on different ports fail #42898

---
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: my-gateway
  namespace: default
spec:
  gatewayClassName: cilium
  listeners:
    # Listener 1: MQTT Secure
    - name: mqtts
      hostname: mqtt.example.com
      port: 8883
      protocol: TLS
      tls:
        mode: Passthrough
    
    # Listener 2: WSS Secure (Same hostname, different port)
    - name: wss
      hostname: mqtt.example.com
      port: 8443
      protocol: TLS
      tls:
        mode: Passthrough

---
# Route 1: Attaches to the 'mqtts' listener on port 8883
apiVersion: gateway.networking.k8s.io/v1alpha2
kind: TLSRoute
metadata:
  name: route-mqtts
  namespace: default
spec:
  hostnames:
    - mqtt.example.com
  parentRefs:
    - name: my-gateway
      sectionName: mqtts # Explicitly targeting listener 1
  rules:
    - backendRefs:
        - name: mqtt-service
          port: 8883

---
# Route 2: Attaches to the 'wss' listener on port 8443
# This is where the conflict usually manifests
apiVersion: gateway.networking.k8s.io/v1alpha2
kind: TLSRoute
metadata:
  name: route-wss
  namespace: default
spec:
  hostnames:
    - mqtt.example.com
  parentRefs:
    - name: my-gateway
      sectionName: wss # Explicitly targeting listener 2
  rules:
    - backendRefs:
        - name: wss-service
          port: 8443