From 90deacebcec16a37659cd7a0ffc058b1648e97a2 Mon Sep 17 00:00:00 2001 From: Valentin Widmer Date: Tue, 16 Jan 2024 10:50:33 +0100 Subject: [PATCH] Re-run pre-commit hooks --- patterns/vpc-lattice/README.md | 4 ++-- .../charts/demo-application/templates/deployment.yaml | 2 +- .../charts/demo-application/templates/gateway-class.yaml | 2 +- .../charts/demo-application/templates/gateway.yaml | 2 +- .../charts/demo-application/templates/httproute.yaml | 2 +- .../charts/demo-application/templates/service.yaml | 2 +- patterns/vpc-lattice/main.tf | 2 +- patterns/vpc-lattice/outputs.tf | 2 +- 8 files changed, 9 insertions(+), 9 deletions(-) diff --git a/patterns/vpc-lattice/README.md b/patterns/vpc-lattice/README.md index 8de670084b..ed0c46eb0c 100644 --- a/patterns/vpc-lattice/README.md +++ b/patterns/vpc-lattice/README.md @@ -7,7 +7,7 @@ This pattern demonstrates how to expose an EKS cluster hosted application to an ## Scenario -With this soluton we showcase how to configure Amazon VPC Lattice using the AWS Gateway API Controller in order to manage Amazon VPC Lattice resources through native K8S Gateway API objects. This pattern deploys two distinct VPCs with a client application running in one of them and a server application in the other. The server application is deployed inside an EKS cluster and made exposed to the client application through Amazon VPC Lattice which establishes connectivity between the two applications. Further we demonstrate how to configure a custom domain name for the exposed service using Amazon Route53. +With this soluton we showcase how to configure Amazon VPC Lattice using the AWS Gateway API Controller in order to manage Amazon VPC Lattice resources through native K8S Gateway API objects. This pattern deploys two distinct VPCs with a client application running in one of them and a server application in the other. The server application is deployed inside an EKS cluster and made exposed to the client application through Amazon VPC Lattice which establishes connectivity between the two applications. Further we demonstrate how to configure a custom domain name for the exposed service using Amazon Route53. ![diagram](assets/diagram.png) @@ -39,4 +39,4 @@ In order to test the connectivty between the client and server, please follow th {% include-markdown "../../docs/_partials/destroy.md" -%} \ No newline at end of file +%} diff --git a/patterns/vpc-lattice/charts/demo-application/templates/deployment.yaml b/patterns/vpc-lattice/charts/demo-application/templates/deployment.yaml index a2dc1de5b6..1b8e744907 100644 --- a/patterns/vpc-lattice/charts/demo-application/templates/deployment.yaml +++ b/patterns/vpc-lattice/charts/demo-application/templates/deployment.yaml @@ -19,4 +19,4 @@ spec: image: public.ecr.aws/x2j8p8w7/http-server:latest env: - name: PodName - value: "server pod" \ No newline at end of file + value: "server pod" diff --git a/patterns/vpc-lattice/charts/demo-application/templates/gateway-class.yaml b/patterns/vpc-lattice/charts/demo-application/templates/gateway-class.yaml index 23f16a9ef0..d4a925745f 100644 --- a/patterns/vpc-lattice/charts/demo-application/templates/gateway-class.yaml +++ b/patterns/vpc-lattice/charts/demo-application/templates/gateway-class.yaml @@ -3,4 +3,4 @@ kind: GatewayClass metadata: name: amazon-vpc-lattice spec: - controllerName: application-networking.k8s.aws/gateway-api-controller \ No newline at end of file + controllerName: application-networking.k8s.aws/gateway-api-controller diff --git a/patterns/vpc-lattice/charts/demo-application/templates/gateway.yaml b/patterns/vpc-lattice/charts/demo-application/templates/gateway.yaml index ca0e22f54c..29e842cbeb 100644 --- a/patterns/vpc-lattice/charts/demo-application/templates/gateway.yaml +++ b/patterns/vpc-lattice/charts/demo-application/templates/gateway.yaml @@ -8,4 +8,4 @@ spec: listeners: - name: http protocol: HTTP - port: 80 \ No newline at end of file + port: 80 diff --git a/patterns/vpc-lattice/charts/demo-application/templates/httproute.yaml b/patterns/vpc-lattice/charts/demo-application/templates/httproute.yaml index 862a2eeef1..e708960296 100644 --- a/patterns/vpc-lattice/charts/demo-application/templates/httproute.yaml +++ b/patterns/vpc-lattice/charts/demo-application/templates/httproute.yaml @@ -17,4 +17,4 @@ spec: matches: - path: type: PathPrefix - value: / \ No newline at end of file + value: / diff --git a/patterns/vpc-lattice/charts/demo-application/templates/service.yaml b/patterns/vpc-lattice/charts/demo-application/templates/service.yaml index 39680474aa..e6fed42551 100644 --- a/patterns/vpc-lattice/charts/demo-application/templates/service.yaml +++ b/patterns/vpc-lattice/charts/demo-application/templates/service.yaml @@ -8,4 +8,4 @@ spec: ports: - protocol: TCP port: 8090 - targetPort: 8090 \ No newline at end of file + targetPort: 8090 diff --git a/patterns/vpc-lattice/main.tf b/patterns/vpc-lattice/main.tf index bb97073942..c97ac3e641 100644 --- a/patterns/vpc-lattice/main.tf +++ b/patterns/vpc-lattice/main.tf @@ -350,4 +350,4 @@ module "endpoint_sg" { ] tags = local.tags -} \ No newline at end of file +} diff --git a/patterns/vpc-lattice/outputs.tf b/patterns/vpc-lattice/outputs.tf index b1a50fa2de..c952ef95d0 100644 --- a/patterns/vpc-lattice/outputs.tf +++ b/patterns/vpc-lattice/outputs.tf @@ -1,4 +1,4 @@ output "configure_kubectl" { description = "Configure kubectl: make sure you're logged in with the correct AWS profile and run the following command to update your kubeconfig" value = "aws eks update-kubeconfig --name ${module.eks.cluster_name} --alias ${module.eks.cluster_name} --region ${local.region}" -} \ No newline at end of file +}