I'm trying to wrap my head around AWS's Gateway API Controller, which claims to be an implementation of the Kubernetes Gateway API. However, it seems mainly focused on managing east-west traffic between clusters or in hybrid setups, especially since it's tied to the VPC Lattice service. Given that the Gateway API is designed as an ingress replacement for north-south traffic, doesn't this setup feel a bit misleading?
Moreover, the official Gateway API site mentions that there usually won't be multiple meshes in a cluster, hence the Gateway and GatewayClass resources aren't typically used. Yet, with the AWS Gateway API Controller, a Gateway seems necessary for any setup to work. So, am I missing something here? It looks like there's no real north-south support, and the east-west traffic handling doesn't align fully with the spec's intentions. Anyone else notice this?
2 Answers
You're correct in pointing out the discrepancy between what the AWS Gateway API Controller claims to do and what it can actually handle. The necessity of having a Gateway for any setup makes it feel like it doesn’t fully align with the Gateway API's original intent. It'd be great if AWS clarified this—it could save a lot of confusion for everyone trying to implement it!
From what I gather, the AWS Gateway API Controller does handle the standard Gateway API, but its implementation seems limited to specific uses. While it's designed to facilitate communication in cluster environments, it appears to focus mainly on east-west traffic rather than the north-south scenarios you mentioned. This could definitely lead to some confusion about its capabilities. It's worth keeping an eye on updates, though, as AWS might expand its functionalities in the future.
That makes sense! The focus on VPC Lattice does seem to shape its direction. I guess it’s still early days for this service, and we might see more features rolled out later.
Exactly! Clarity on its intended use cases would definitely help. Navigating through these services can be frustrating when the documentation isn’t aligned with actual functionality.