Skip to content
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.

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

Support AWS RAM Resource Sharing for VPC Lattice Services in Gateway API Controller #697

Open
gadiener opened this issue Feb 3, 2025 · 0 comments

Comments

@gadiener
Copy link

gadiener commented Feb 3, 2025

The Gateway API controller automatically associates VPC Lattice services with a service network. However, according to the AWS documentation on the "Centralized VPC Lattice service network" model, providers are encouraged to share VPC Lattice services across different accounts using AWS RAM. This means the service should first be shared with the network account, allowing them to handle network associations, see Centralized VPC Lattice service network.

Currently, the Gateway API controller does not support this AWS RAM sharing process. As a result, it automatically tries to associate the VPC Lattice service with the service network, which limits the ability to follow the recommended centralized management approach.

It would be great to have the option in the Gateway API controller to create an AWS RAM resource share for VPC Lattice services created via HTTPRoute. This feature would enable:

  • Providers to share VPC Lattice services with a specified network account via AWS RAM.
  • The network management account to handle service network associations independently using their own automation tools.

There's already an ongoing issue focused on preventing automatic network associations for VPC Lattice services, which you can track here: #691

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant