Skip to content

Docs: mention north/south traffic #723

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 30, 2025
Merged

Docs: mention north/south traffic #723

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/concepts/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,14 @@ With VPC Lattice you can also avoid some of these common problems:
- **Sidecar management**: Changes to sidecars might require those sidecars to be reconfigured or rebooted.
While this might not be a big issue for a handful of sidecars, it can be disruptive if you have thousands of pods, each with its own sidecar.

## Limitations

For those already familiar with the reference implementation of [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/), the API generally serves two purposes: enabling routing for both North-South (Ingress) and also East-West (Mesh) traffic.

The AWS Gateway API Controller is currently focused only on East-West (Mesh) traffic through VPC Lattice.

Many users will expect North-South (Ingress) ALB/NLB-type features. This is available (still using the v1 Ingress spec) from the [AWS Load Balancer Controller](https://github.com/kubernetes-sigs/aws-load-balancer-controller)

## Relationship between VPC Lattice and Kubernetes

As a Kubernetes user, you can have a very Kubernetes-native experience using the VPC Lattice APIs.
Expand Down