feat: Blueprint for VPC lattice with kubernetes api controllers

[neelaruban]

Description

Provisioning VPC Lattice and use the API gateway controller to connect services across EKS clusters

Motivation and Context

• Resolves Blueprint for VPC Lattice #1638
• Resolves # 312

How was this change tested?

• Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
• Yes, I have updated the docs for this feature
• Yes, I ran pre-commit run -a with this PR

Additional Notes

[allamand]

• There is no version engine defined for the RDS module, it does not deploy.
• Does RDS is needed for this pattern ? seems we can simplify by having simpler deployment
• you should have output.tf so that users can connect to the cluster by executing the output (see others patterns for reference)

[allamand]

Thanks for updated, is it working on your side ? My targets groups are not able to join the pods on my side

[bryantbiggs]

Lets remove all of the database dependencies unless there is a strong reason why this needs to be included in the pattern

[neelaruban]

I got this idea from a blog post that's already linked to this problem/request which depends upon the aurora RDS .
https://aws.amazon.com/blogs/containers/application-networking-with-amazon-vpc-lattice-and-amazon-eks/

i am happy to work on a different scenario if you could direct me in the right direction

[neelaruban]

Thanks for updated, is it working on your side ? My targets groups are not able to join the pods on my side

let me test it again

[neelaruban]

As it turns out the current version of EKS blueprint addon needs extra permissions for the aws gateway api controller to create httproutes , i have already issued a PR to fix it
could someone please look into it , thanks
tracked issue

[neelaruban]

@allamand @bryantbiggs I have introduced new workloads for the VPC lattice patterns with the gateway API controllers, Could you please review them :D

[github-actions]

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

[neelaruban]

@allamand please let me know if my latest changes are sufficient to merge this PR , thanks

[allamand]

@neelaruban rhere was an issue with VPC lattice controller v1.0.2 which prevented service import to work properly. This is now fixed in latest release v1.0.3. In the meantime we actually have 2 PRs for lattice. We are working to have different use cases in same pattern starting with the other one which is simpler. In my opinion the real value will be to focus on cross cluster flows with TLS encryption and IAM authorizations.

What I suggest would be to adapt your actual pattern to be a use-case dedicated to microservices flows sécurisation. (Merge the code as new use case in the other VPC lattice pattern, and add examples for iam auth). I can help with this

[github-actions]

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

[github-actions]

Pull request closed due to inactivity.