release artifacts for release v0.0.18

docs/deploy.md

@@ -77,7 +77,7 @@ Run through them again for a second cluster to use with the extended example sho
    ```
 8. Run either `kubectl` or `helm` to deploy the controller:
    ```bash
-   kubectl apply -f examples/deploy-v0.0.17.yaml
+   kubectl apply -f examples/deploy-v0.0.18.yaml
    ```
    or
    ```bash
@@ -86,7 +86,7 @@ Run through them again for a second cluster to use with the extended example sho
    # 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=v0.0.17 \
+      --version=v0.0.18 \
       --set=serviceAccount.create=false --namespace aws-application-networking-system \
       # awsRegion, clusterVpcId, clusterName, awsAccountId are required for case where IMDS is NOT AVAILABLE, e.g Fargate, self-managed clusters with IMDS access blocked 
       --set=awsRegion= \

helm/Chart.yaml

@@ -1,8 +1,8 @@
 apiVersion: v1
 name: aws-gateway-controller-chart
 description: A Helm chart for the Gateway Controller for AWS VPC Lattice
-version: v0.0.17
-appVersion: v0.0.17
+version: v0.0.18
+appVersion: v0.0.18
 home: https://github.com/aws/aws-application-networking-k8s
 icon: https://raw.githubusercontent.com/aws/eks-charts/master/docs/logo/aws.png
 sources:

helm/values.yaml

@@ -4,7 +4,7 @@
 
 image:
   repository: public.ecr.aws/aws-application-networking-k8s/aws-gateway-controller
-  tag: v0.0.17
+  tag: v0.0.18
   pullPolicy: IfNotPresent
   pullSecrets: []