Skip to content

Commit 12b3531

Browse files
authored
Updated User Guide for latest release (#92)
1 parent bb8026b commit 12b3531

File tree

1 file changed

+9
-5
lines changed

1 file changed

+9
-5
lines changed

docs/deploy.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,13 +3,17 @@
33
Follow these instructions to create a cluster and deploy the AWS Gateway API Controller.
44
Run through them again for a second cluster to use with the extended example shown later.
55

6+
1. Set your region (us-west-2 or us-east-1) as an environment variable. For example:
7+
```bash
8+
export AWS_REGION=us-west-2
9+
```
610
1. You can use an existing EKS cluster or create a new one as shown here:
711
```bash
8-
eksctl create cluster --name <my-cluster> --region us-west-2
12+
eksctl create cluster --name <my-cluster> --region $AWS_REGION
913
```
1014
1. Configure security group: To receive traffic from the VPC Lattice fleet, you must set up security groups so that they allow all Pods communicating with VPC Lattice to allow traffic on all ports from the 169.254.171.0/24 address range. See [Control traffic to resources using security groups](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html) for details. You can use the following managed prefix to provide the values:
1115
```bash
12-
aws ec2 get-managed-prefix-list-entries --region us-west-2 --prefix-list-id pl-0721453c7ac4ec009
16+
aws ec2 get-managed-prefix-list-entries --region $AWS_REGION --prefix-list-id pl-0721453c7ac4ec009
1317
```
1418
```
1519
ENTRIES 169.254.171.0/24
@@ -57,14 +61,14 @@ Run through them again for a second cluster to use with the extended example sho
5761
--name=gateway-api-controller \
5862
--attach-policy-arn=$VPCLatticeControllerIAMPolicyArn \
5963
--override-existing-serviceaccounts \
60-
--region us-west-2 \
64+
--region $AWS_REGION \
6165
--approve
6266
```
6367

6468
1. Run either `kubectl` or `helm` to deploy the controller:
6569

6670
```bash
67-
kubectl apply -f examples/deploy-v0.0.1.yaml
71+
kubectl apply -f examples/deploy-v0.0.3.yaml
6872
```
6973

7074
or
@@ -76,7 +80,7 @@ Run through them again for a second cluster to use with the extended example sho
7680
helm install gateway-api-controller \
7781
oci://public.ecr.aws/aws-application-networking-k8s/aws-gateway-controller-chart\
7882
--version=v0.0.2 \
79-
--set=aws.region=us-west-2 --set=serviceAccount.create=false --namespace system
83+
--set=aws.region=$AWS_REGION --set=serviceAccount.create=false --namespace system
8084
```
8185

8286
1. Create the amazon-vpc-lattice GatewayClass:

0 commit comments

Comments
 (0)