Support LACP networking configuration for EKSA BareMetal
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
**What would you like to be added**:
EKSA Bare Metal documentation shows Advanced Bare Metal Cluster Configuration [1]. There are no docs on LACP networking Configuration. Workaround [2] [3] from Cilium GitHub issue with few details.
[1] https://anywhere.eks.amazonaws.com/docs/getting-started/baremetal/bare-spec/#advanced-bare-metal-cluster-configuration
[2] https://github.com/cilium/cilium/issues/18706
[3] https://github.com/cilium/cilium/issues/18706#issuecomment-1031572546
**Why is this needed**:
- High Avaialbility, Load Balancing, Scalability and to support High performance networks.
- Example: Telco or Streaming use cases.
Contributor guide
Research direction
Start with the Advanced Bare Metal Cluster Configuration documentation linked as [1], then read the configuration details and workaround in the Cilium issue and comment linked as [2] and [3]. Document the supported LACP networking configuration for EKSA Bare Metal, including enough setup detail for the stated high-availability and performance use cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation, networking
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100