Merge branch 'main' into issue/691

Author: Ryan Lymburner

docs/faq.md

@@ -112,4 +112,8 @@ Standalone services require explicit configuration for cross-VPC communication:
 2. **VPC peering or Transit Gateway** for network connectivity
 3. **Manual service network association** in target VPCs
 
-Service network associated services automatically handle cross-VPC communication within the same service network.
+Service network associated services automatically handle cross-VPC communication within the same service network.
+
+**How do I prevent 503 errors during deployments?**
+
+When using AWS Gateway API Controller with EKS, customers may experience 503 errors during deployments due to a timing gap between pod termination and VPC Lattice configuration propagation, which affects the time controller takes to deregister a terminating pod. We recommend setting `terminationGracePeriod` to at least 150 seconds and implementing a preStop hook that has a sleep of 60 seconds (but no more than the `terminationGracePeriod`). For optimal performance, also consider setting `ROUTE_MAX_CONCURRENT_RECONCILES` to 10 which further accelerates the pod deregistration process, regardless of the number of targets.