aws-application-networking-k8s
aws-application-networking-k8s copied to clipboard
Unable to Configure Gateway API with AWS VPC Lattice Using gateway-api-controller
I am facing issues configuring the gateway-api-controller to work with AWS VPC Lattice for my Kubernetes Gateway API setup. Specifically, the Gateway resource is stuck in a Programmed: False state, with the following message in the status
VPC Lattice Service Network not found
I have followed the setup as outlined in the documentation, but the Gateway is unable to connect to the VPC Lattice Service Network. Below is a detailed description of the configuration and the issues encountered.
2. The Gateway is created but remains unprogrammed.
kubectl describe gateway portfolio-gateway output:
status: Conditions: Last Transition Time: 2024-09-20T13:06:24Z Message: VPC Lattice Service Network not found Observed Generation: 1 Reason: Pending Status: False Type: Programmed
3. Logs from the controller:
{"level":"info","ts":"2024-09-19T12:00:41.253Z","logger":"controller.route","caller":"gateway/model_build_lattice_service.go:140","msg":"No custom-domain-name for route portfolio-http-route-aws-application-networking-system"} {"level":"info","ts":"2024-09-19T12:00:41.843Z","logger":"controller.route","caller":"controllers/route_controller.go:155","msg":"reconcile error","name":"portfolio-http-route","message":"error during service synthesis failed ServiceManager.Upsert portfolio-http-route-aws-application-ne due to not found, Service network portfolio-gateway"}
Expected Behavior: The Gateway should be Programmed: True and route traffic to the backend service via the VPC Lattice.
Observed Behavior: The Gateway remains in a Programmed: False state with the error message "VPC Lattice Service Network not found."
Troubleshooting Steps Taken:
- Verified that the VPC Lattice Service Network exists and is accessible.
- Confirmed the gateway-api-controller is running and has the correct permissions.
- Followed the documentation for configuring Gateway API with AWS VPC Lattice.
- The IAM permissions seem correct, but the controller is unable to synthesize or connect to the VPC Lattice Service Network.
Environment:
- Kubernetes version: v1.30
- Gateway API version: v1beta1
- AWS environment with VPC Lattice
- gateway-api-controller used as per AWS documentation
Additional Information: Please let me know if there is any additional configuration or debugging steps I should follow to resolve this issue. Your help is greatly appreciated!