Merge branch 'main' into vbedi_issue724

Author: Ryan Lymburner

README.md

@@ -55,5 +55,5 @@ This project is licensed under the Apache-2.0 License.
 [getting-started]: https://www.gateway-api-controller.eks.aws.dev/guides/getstarted/
 [spec]: https://www.gateway-api-controller.eks.aws.dev/api-reference/
 [concepts]: https://www.gateway-api-controller.eks.aws.dev/concepts/
-[gh_release]: https://github.com/aws/aws-application-networking-k8s/releases/tag/v1.1.6
+[gh_release]: https://github.com/aws/aws-application-networking-k8s/releases/tag/v1.1.7
 [godoc]: https://www.gateway-api-controller.eks.aws.dev/

config/manager/kustomization.yaml

@@ -13,4 +13,4 @@ configMapGenerator:
 images:
 - name: controller
   newName: public.ecr.aws/aws-application-networking-k8s/aws-gateway-controller
-  newTag: v1.1.6
+  newTag: v1.1.7

docs/concepts/overview.md

@@ -53,7 +53,7 @@ In the context of Kubernetes, Amazon VPC Lattice helps to simplify the following
   After configuring your services with the AWS Gateway API Controller, you can facilitate advanced traffic management and application layer routing between services on those clusters without dealing with the underlying infrastructure.
   VPC Lattice handles a lot of the details for you without needing things like sidecars.
 
-  **Multi-cluster health check consistency**: When using TargetGroupPolicy with ServiceExport resources, health check configurations are automatically propagated across all clusters participating in the service mesh. This ensures consistent health monitoring behavior regardless of which cluster contains the route resource, eliminating configuration drift and improving reliability in multi-cluster deployments.
+-  **Multi-cluster health check consistency**: When using TargetGroupPolicy with ServiceExport resources, health check configurations are automatically propagated across all clusters participating in the service mesh. This ensures consistent health monitoring behavior regardless of which cluster contains the route resource, eliminating configuration drift and improving reliability in multi-cluster deployments.
 - **Cross-platform access**: VPC Lattice allows access to serverless and Amazon EC2 features, as well as Kubernetes cluster features.
   This gives you a way to have a consistent interface to multiple types of platforms.
 - **Implement a defense-in-depth strategy**: Secure communication between services and networks.

docs/guides/deploy.md

@@ -191,7 +191,7 @@ aws ecr-public get-login-password --region us-east-1 | helm registry login --use
 # Run helm with either install or upgrade
 helm install gateway-api-controller \
     oci://public.ecr.aws/aws-application-networking-k8s/aws-gateway-controller-chart \
-    --version=v1.1.6 \
+    --version=v1.1.7 \
     --set=serviceAccount.create=false \
     --namespace aws-application-networking-system \
     --set=log.level=info # use "debug" for debug level logs
@@ -200,7 +200,7 @@ helm install gateway-api-controller \
 === "Kubectl"
 
 ```bash
-kubectl apply -f https://raw.githubusercontent.com/aws/aws-application-networking-k8s/main/files/controller-installation/deploy-v1.1.6.yaml
+kubectl apply -f https://raw.githubusercontent.com/aws/aws-application-networking-k8s/main/files/controller-installation/deploy-v1.1.7.yaml
 ```
 
 1. Create the `amazon-vpc-lattice` GatewayClass:

docs/guides/getstarted.md

@@ -43,7 +43,7 @@ This example creates a single cluster in a single VPC, then configures two HTTPR
         aws ecr-public get-login-password --region us-east-1 | helm registry login --username AWS --password-stdin public.ecr.aws
         helm upgrade gateway-api-controller \
         oci://public.ecr.aws/aws-application-networking-k8s/aws-gateway-controller-chart \
-        --version=v1.1.6 \
+        --version=v1.1.7 \
         --reuse-values \
         --namespace aws-application-networking-system \
         --set=defaultServiceNetwork=my-hotel 
@@ -222,7 +222,7 @@ This section builds on the previous one. We will be migrating the Kubernetes `in
         aws ecr-public get-login-password --region us-east-1 | helm registry login --username AWS --password-stdin public.ecr.aws
         helm upgrade gateway-api-controller \
         oci://public.ecr.aws/aws-application-networking-k8s/aws-gateway-controller-chart \
-        --version=v1.1.6 \
+        --version=v1.1.7 \
         --reuse-values \
         --namespace aws-application-networking-system \
         --set=defaultServiceNetwork=my-hotel