Create a httproute without any rule cannot make controller invoke the VPCLattice createService() and createServiceNetworkServiceAssociation() api

[zijun726911]

If I don't put rules section when define a HTTPRoute for example:

apiVersion: gateway.networking.k8s.io/v1beta1
kind: HTTPRoute
metadata:
  name: my-route
spec:
  parentRefs:
    - name: my-gw
      sectionName: http

The controller will not start to synthesize VPC lattice service and serviceNetworkServiceAssociation for my-route (one k8s http correspond to one vpclatticeService)

2023-04-10T09:20:44Z	DEBUG	events	Adding/Updating Reconcile	{"type": "Normal", "object": {"kind":"HTTPRoute","namespace":"default","name":"account2-route2","uid":"429f0ac8-ce98-4465-bfe0-22fb830ff969","apiVersion":"gateway.networking.k8s.io/v1beta1","resourceVersion":"1211628"}, "reason": "Reconcile"}
2023-04-10T09:20:44Z	DEBUG	events	Failed build model due to LATTICE_RETRY	{"type": "Warning", "object": {"kind":"HTTPRoute","namespace":"default","name":"account2-route2","uid":"429f0ac8-ce98-4465-bfe0-22fb830ff969","apiVersion":"gateway.networking.k8s.io/v1beta1","resourceVersion":"1211628"}, "reason": "FailedBuildModel"}

Hoping the controller can invoke the VPC lattice createService() (as well as listService() and identifer whether this vpc lattice service has already been created) and createServiceNetworkServiceAssociation() apis for a httproute that don't have any rule. this is useful becuase for the Resource Access Manager sharing VPC Lattice's service scenario, the sharee account's ServiceNetwork should be able to associate to sharer account's service, while don't create listeners and rules for this servoce, because sharee account don't have any permission to create listeners and rules for sharee account's vpc lattice service

[liwenwu-amazon]

Here is one workaround for this:
Through VPC lattice console or CLI, K8S user can associate this service to the service network (gateway). And then the cluster can access this service