[EKS] [CNI Feature request]: Support Inter-node encryption
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
**Tell us about your request**
Enable inter-node encryption within the AWS VPC CNI
**Which service(s) is this request for?**
EKS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
We are required to ensure inter node traffic is encrypted. At present we can do this using Cilium in chaining mode as per https://aws.amazon.com/blogs/containers/transparent-encryption-of-node-to-node-traffic-on-amazon-eks-using-wireguard-and-cilium/. This introduces a supportability issue where we require multiple vendors to troubleshoot an issue if required. Ideally we would like this to be a AWS "in-house" solution, whether that is a AWS supported configuration of Cilium, given EKS anywhere is using cilium, or done via the AWS CNI. Obviously we could go full service mesh but again it it introduces questions around supportability
**Are you currently working around this issue?**
We are doing this at present https://aws.amazon.com/blogs/containers/transparent-encryption-of-node-to-node-traffic-on-amazon-eks-using-wireguard-and-cilium/
**Additional context**
This would allow us to back off our support for the networking component to AWS fully, giving us 1 throat to choke , for our base infra
**Attachments**
Contributor guide
Research direction
Start by reading the linked AWS blog describing WireGuard and Cilium chaining, then compare that workaround with the requested AWS-supported configuration or AWS CNI approach. Done means EKS inter-node traffic can be encrypted through an AWS-supported solution with clear supportability boundaries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100