Skip to content

Commit fb10944

Browse files
authored
Added helm command and managed prefix list info (#63)
* Added helm command and managed prefix list info * Fixed small goof
1 parent 2415f99 commit fb10944

File tree

1 file changed

+20
-3
lines changed

1 file changed

+20
-3
lines changed

docs/how-it-works.md

Lines changed: 20 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,8 +29,13 @@ Run through them again for a second cluster to use with the extended example sho
2929
```bash
3030
eksctl create cluster --name <my-cluster> --region us-west-2
3131
```
32-
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.
33-
32+
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:
33+
```bash
34+
aws ec2 get-managed-prefix-list-entries --region us-west-2 --prefix-list-id pl-0721453c7ac4ec009
35+
```
36+
```
37+
ENTRIES 169.254.171.0/24
38+
```
3439
1. Create an IAM OIDC provider: See [Creating an IAM OIDC provider for your cluster](https://docs.aws.amazon.com/eks/latest/userguide/enable-iam-roles-for-service-accounts.html) for details.
3540
```bash
3641
eksctl utils associate-iam-oidc-provider --cluster <my-cluster> --approve
@@ -78,10 +83,22 @@ Run through them again for a second cluster to use with the extended example sho
7883
--approve
7984
```
8085

81-
1. Run the following to deploy the controller:
86+
1. Run either `kubectl` or `helm` to deploy the controller:
87+
8288
```bash
8389
kubectl apply -f examples/deploy-v0.0.1.yaml
8490
```
91+
or
92+
93+
```bash
94+
# login to ECR
95+
aws ecr-public get-login-password --region us-east-1 | helm registry login --username AWS --password-stdin public.ecr.aws
96+
# Run helm with either install or upgrade
97+
helm install gateway-api-controller \
98+
oci://public.ecr.aws/aws-application-networking-k8s/aws-gateway-controller-chart\
99+
--version=v0.0.2 \
100+
--set=aws.region=us-west-2 --set=serviceAccount.create=false --namespace system
101+
```
85102

86103
1. Create the amazon-vpc-lattice GatewayClass:
87104
```bash

0 commit comments

Comments
 (0)