-
Notifications
You must be signed in to change notification settings - Fork 3.4k
ip-masq-agent: refactor into a Hive Cell #40347
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
Conversation
/test |
/test Looks like I'm not allowed to run tests on draft PRs? 😞 |
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice cleanup! Some feedbacks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@YutaroHayakawa already commented on the things I also noticed. Will approve assuming those comments are addressed before merge.
/test |
1 similar comment
/test |
/ci-runtime |
/test |
/test |
Signed-off-by: Anton Ippolitov <anton.ippolitov@datadoghq.com>
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now, looks good to me. Thanks!
Description
This PR wraps the existing
ip-masq-agent
code into a Hive Cell. This goes in-line with the current efforts to modularize the codebase and is a pre-requisite for #40141.The
ip-masq-agent
and its Maps used to be created inside the Legacy Daemon Cell. Both the Agent and its Maps are now modularized and are created before the Daemon Cell starts.Testing
On top of unit tests, I also tried the PR in a real cluster. Unfortunately I don't have an easy way to setup a 1.18 environment so I backported my change to 1.17.5. I then verified that:
--enable-ip-masq-agent=false
:--enable-ip-masq-agent=true
:module=agent.controlplane.ip-masq-agent
cilium status
shows correctly:--ip-masq-agent-config-path
option is taken into account and the BPF Map is populated with the expected values from the config path: