precommit format update

Author: vara-bonthu

LICENSE

@@ -198,4 +198,4 @@
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
-   limitations under the License.
+   limitations under the License.

NOTICE.txt

@@ -4,4 +4,4 @@ Licensed under the Apache License, Version 2.0 (the "License"). You may not use
 
     http://aws.amazon.com/apache2.0/
 
-or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
+or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

docs/add-ons/external-dns.md

@@ -1,6 +1,6 @@
 # ExternalDNS
 
-[External DNS](https://github.com/kubernetes-sigs/external-dns) is a Kubernetes add-on that can automate the management of DNS records based on Ingress and Service resources. 
+[External DNS](https://github.com/kubernetes-sigs/external-dns) is a Kubernetes add-on that can automate the management of DNS records based on Ingress and Service resources.
 
 For complete project documentation, please visit the [External DNS Github repository](https://github.com/kubernetes-sigs/external-dns).
 

examples/eks-cluster-with-external-dns/README.md

@@ -1,28 +1,28 @@
 # EKS Cluster with External DNS
 
-This example demonstrates how to leverage External DNS, in concert with Ingress Nginx and AWS Load Balancer Controller. It demonstrates how you can easily provision multiple services with secure, custom domains which sit behind a single load balancer. 
+This example demonstrates how to leverage External DNS, in concert with Ingress Nginx and AWS Load Balancer Controller. It demonstrates how you can easily provision multiple services with secure, custom domains which sit behind a single load balancer.
 
 The pattern deploys the sample workloads that reside in the [EKS Blueprints Workloads repo](https://github.com/aws-samples/eks-blueprints-workloads) via ArgoCD. The [configuration for `team-riker`](https://github.com/aws-samples/eks-blueprints-workloads/tree/main/teams/team-riker/dev/templates) will deploy an Ingress resource which contains configuration for both path-based routing and the custom hostname for the `team-riker` service. Once the pattern is deployed, you will be able to reach the `team-riker` sample workload via a custom domain you supply.
 
 ## How to Deploy
 
 ### Prerequisites:
 
-#### Tools 
+#### Tools
 
 Ensure that you have installed the following tools in your Mac or Windows Laptop before start working with this module and run Terraform Plan and Apply
 1. [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html)
 3. [Kubectl](https://Kubernetes.io/docs/tasks/tools/)
 4. [Terraform](https://learn.hashicorp.com/tutorials/terraform/install-cli)
 
-#### AWS Resources 
+#### AWS Resources
 
 This example requires the following AWS resources:
 
-* A Route53 Hosted Zone for a domain that you own. 
-* A SSL/TLS certificate for your domain stored in AWS Certificate Manager (ACM). 
- 
-For information on Route53 Hosted Zones, [see Route53 documentation](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zones-working-with.html). For instructions on requesting a SSL/TLS certificate for your domain, see [ACM docs](https://docs.aws.amazon.com/acm/latest/userguide/gs.html). 
+* A Route53 Hosted Zone for a domain that you own.
+* A SSL/TLS certificate for your domain stored in AWS Certificate Manager (ACM).
+
+For information on Route53 Hosted Zones, [see Route53 documentation](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zones-working-with.html). For instructions on requesting a SSL/TLS certificate for your domain, see [ACM docs](https://docs.aws.amazon.com/acm/latest/userguide/gs.html).
 
 ### Deployment Steps
 
@@ -43,7 +43,7 @@ terraform init
 
 #### Step3: Replace placeholder values in terraform.tfvars
 
-Both values in `terraform.tfvars` must be updated. 
+Both values in `terraform.tfvars` must be updated.
 
 * `eks_cluster_domain` - the domain for your cluster. Value is used to look up a Route53 Hosted Zone that you own. DNS records created by `ExternalDNS` will be created in this Hosted Zone.
 * `acm_certificate_domain` - the domain for a certificate in ACM that will be leveraged by `Ingress Nginx`. Value is used to look up an ACM certificate that will be used to terminate HTTPS connections. This value should likely be a wildcard cert for your `eks_cluster_domain`.  

modules/kubernetes-addons/aws-load-balancer-controller/values.yaml

@@ -1,2 +1,2 @@
 clusterName: ${eks_cluster_id}
-region: ${aws_region}
+region: ${aws_region}

modules/kubernetes-addons/external-dns/README.md

@@ -2,7 +2,7 @@
 
 ## Introduction
 
-[External DNS](https://github.com/kubernetes-sigs/external-dns) is a Kubernetes add-on that can automate the management of DNS records based on Ingress and Service resources. 
+[External DNS](https://github.com/kubernetes-sigs/external-dns) is a Kubernetes add-on that can automate the management of DNS records based on Ingress and Service resources.
 
 For complete project documentation, please visit the [ExternalDNS Github repository](https://github.com/kubernetes-sigs/external-dns).
 

modules/kubernetes-addons/external-dns/values.yaml

@@ -1,4 +1,4 @@
 provider: aws
 zoneIdFilters: ${zone_filter_ids}
 aws:
-  region: ${aws_region}
+  region: ${aws_region}

modules/kubernetes-addons/traefik/main.tf

@@ -16,4 +16,4 @@ resource "kubernetes_namespace_v1" "this" {
       "app.kubernetes.io/managed-by" = "terraform-eks-blueprints"
     }
   }
-}
+}