You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/how-it-works.md
+9-8Lines changed: 9 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,15 +12,15 @@ With the controller deployed and running, you will be able to manage services fo
12
12
13
13
While separating the application developer from the details of the underling infrastructure, the controller also provides a Kubernetes-native experience, rather than creating a lot of new AWS ways of managing services.
14
14
It does this by integrating with the Kubernetes Gateway API.
15
-
This lets you work with Kubernetes service-related resources using Kubernetes APIs and custom resource definitions (CRDs).
15
+
This lets you work with Kubernetes service-related resources using Kubernetes APIs and custom resource definitions (CRDs) defined by the Kubernetes [networking.k8s.io specification](https://gateway-api.sigs.k8s.io/references/spec/).
16
16
17
17
For more information on this technology, see [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/).
18
18
19
19
A few things to keep in mind:
20
20
* If you are new to the VPC Lattice service, keep in mind that names you use for objects must be unique across your entire account and not just across each cluster used by that account.
21
21
* Your AWS CNI must be v1.8.0 or later to work with VPC Lattice.
22
22
23
-
## Deploying the Gateway API Controller
23
+
## Deploying the AWS Gateway API Controller
24
24
25
25
Follow these instructions to create a cluster and deploy the AWS Gateway API Controller.
26
26
Run through them again for a second cluster to use with the extended example shown later.
@@ -43,12 +43,12 @@ Run through them again for a second cluster to use with the extended example sho
43
43
{
44
44
"Effect": "Allow",
45
45
"Action": [
46
-
"vpc-lattice:",
46
+
"vpc-lattice:*",
47
47
"iam:CreateServiceLinkedRole",
48
48
"ec2:DescribeVpcs",
49
49
"ec2:DescribeSubnets"
50
50
],
51
-
"Resource": ""
51
+
"Resource": "*"
52
52
}
53
53
]
54
54
}
@@ -82,10 +82,11 @@ Run through them again for a second cluster to use with the extended example sho
82
82
kubectl apply -f examples/deploy-v0.0.1.yaml
83
83
```
84
84
85
-
## Using the Gateway API Controller
85
+
## Using the AWS Gateway API Controller
86
86
87
87
The first part of this section provides an example of setting up of service-to-service communications on a single cluster.
88
88
The second section extends that example by creating another inventory service on a second cluster on a different VPC, and spreading traffic to that service across the two clusters and VPCs.
89
+
Both clusters are created using `eksctl`, with both clusters created from the same account by the same cluster admin.
89
90
90
91
### Set up single-cluster/VPC service-to-service communications
91
92
@@ -239,7 +240,7 @@ The following figure illustrates this:
239
240
240
241
1. Switch you credentials to use the second cluster
241
242
242
-
1. Create a Kubernetes inventory in the second cluster:
243
+
1. Create a Kubernetes inventory-ver2 service in the second cluster:
243
244
```bash
244
245
kubectl apply -f examples/inventory-ver2.yaml
245
246
```
@@ -336,9 +337,9 @@ With VPC Lattice you can also avoid some of these common problems:
336
337
### Relationship between VPC Lattice and Kubernetes
337
338
338
339
As a Kubernetes user, you can have a very Kubernetes-native experience using the VPC Lattice APIs.
339
-
The following figure illustrates how VPC Lattice object connect to [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/) objects:
340
+
The following figure illustrates how VPC Lattice objects connect to [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/) objects:
340
341
341
-
[Image: VPCLatticeToKubernetesGatewayAPI.png]
342
+

342
343
343
344
As shown in the figure, there are different personas associated with different levels of control in VPC Lattice.
344
345
Notice that the Kubernetes Gateway API syntax is used to create the gateway, HTTPRoute and services, but Kubernetes gets the details of those items from VPC Lattice:
0 commit comments