2.0 IOR should not create Route for egress GW

Using servicemeshoperator v2.0.2 and OCP 4.7, if I create an egress Gateway:

apiVersion: networking.istio.io/v1beta1
kind: Gateway
metadata:
  name: requestbin-egress
spec:
  selector:
    istio: egressgateway
  servers:
  - port:
      number: 80
      name: http
      protocol: HTTP
    hosts:
    - xxxxx.m.pipedream.net
 
The IOR creates a corresponding Route in the istio-system namespace:
 
apiVersion: route.openshift.io/v1
kind: Route
metadata:
  annotations:
    maistra.io/original-host: enxemyu5mtjqcrx.m.pipedream.net
  creationTimestamp: "2021-03-11T01:15:43Z"
  generateName: istio-testapp-requestbin-egress-
  labels:
    maistra.io/gateway-name: requestbin-egress
    maistra.io/gateway-namespace: istio-testapp
    maistra.io/gateway-resourceVersion: "4333894"
    maistra.io/generated-by: ior

 ...

  name: istio-testapp-requestbin-egress-96kp2
  namespace: istio-system
  resourceVersion: "4333907"
  uid: 6b120b4f-2c8f-419d-a0f3-c57f2a2d5d61
spec:
  host: enxemyu5mtjqcrx.m.pipedream.net
  port:
    targetPort: http2
  to:
    kind: Service
    name: istio-egressgateway
    weight: 100
  wildcardPolicy: None
status:
  ingress:
  - conditions:
    - lastTransitionTime: "2021-03-11T01:15:43Z"
      status: "True"
      type: Admitted
    host: enxemyu5mtjqcrx.m.pipedream.net
    routerCanonicalHostname: apps.cluster-cbb5.sandbox1118.opentlc.com
    routerName: default
    wildcardPolicy: None
 
I don't think this route should be created. The example GW is an egress GW not an ingress GW.