Controller is not populating the status field of HTTPRouteRule #104
Description
When deploying the examples/rate-route-path.yaml, the VPC Lattice Service is created and associated to the my-hotel Service Network. However, the status field of the HTTPRoute is not populated.
» kubectl get httproute rates -o yaml
apiVersion: gateway.networking.k8s.io/v1alpha2
kind: HTTPRoute
metadata:
annotations:
application-networking.k8s.aws/lattice-assigned-domain-name: rates-default-0faed837f54892c34.7d67968.vpc-lattice-svcs.us-west-2.on.aws
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"gateway.networking.k8s.io/v1alpha2","kind":"HTTPRoute","metadata":{"annotations":{},"name":"rates","namespace":"default"},"spec":{"parentRefs":[{"name":"my-hotel","sectionName":"http"}],"rules":[{"backendRefs":[{"kind":"Service","name":"parking","port":8090}],"matches":[{"path":{"type":"PathPrefix","value":"/parking"}}]},{"backendRefs":[{"kind":"Service","name":"review","port":8090}],"matches":[{"path":{"type":"PathPrefix","value":"/review"}}]}]}}
creationTimestamp: "2023-02-24T23:57:00Z"
finalizers:
- httproute.k8s.aws/resources
generation: 1
name: rates
namespace: default
resourceVersion: "250637"
uid: d923b7fb-0091-4634-ad78-44e7223160a0
spec:
parentRefs:
- group: gateway.networking.k8s.io
kind: Gateway
name: my-hotel
sectionName: http
rules:
- backendRefs:
- group: ""
kind: Service
name: parking
port: 8090
weight: 1
matches:
- path:
type: PathPrefix
value: /parking
- backendRefs:
- group: ""
kind: Service
name: review
port: 8090
weight: 1
matches:
- path:
type: PathPrefix
value: /review
The VPC Lattice Service is created and working.
According to the RouteStatus spec: which defines the common attributes that all Routes MUST include within their status.
There is a single field parents in the status.
Parents is a list of parent resources (usually Gateways) that are associated with the route, and the status of the route with respect to each parent. When this route attaches to a parent, the controller that manages the parent must add an entry to this list when the controller first sees the route and should update the entry as appropriate when the route or gateway is modified.