[EKS] [eks-node-monitoring-agent] [request]: support hostnetwork configuration
- 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**
Unless there is a reason that this has to run in the hostnetwork, it would be great if there was an option to make that configurable in the addon.
**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're using cilium in overlay mode and prefer to run things with `hostnetwork: false` when possible.
Contributor guide
Research direction
Start by investigating the EKS eks-node-monitoring-agent addon and how its hostnetwork setting is currently defined. Review the interaction with Cilium overlay mode, then determine the configuration surface and compatibility constraints. Done means hostnetwork can be set to false without breaking the agent or its supported EKS behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100