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
docs: ENIs should not be managed by the OS #16186
docs: ENIs should not be managed by the OS #16186
Conversation
When ENIs are managed by services such as NetworkManager or systemd-networkd, it can happen that they interfere with Cilium's configuration. For example, systemd-networkd can remove the ENI IP assigned by Cilium if the carrier is temporarily down, thus breaking SNAT. We previously had a similar section regarding NetworkManager and DHCP in the EKS installation guide, but the EKS guide has since been replaced by the Cilium CLI installation guide. This section here therefore acts as a replacement and states that the devices need to be unmanaged (e.g. disabling DHCP is not enough for systemd-networkd). Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
|
||
.. tabs:: | ||
|
||
.. group-tab:: Network Manager |
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.
For future reference these tabs don't need to be grouped, I think basic tabs would work too. But not an issue and it's not as if we paid a lot of attention to it in the rest of the documentation anyway.
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.
I actually didn't know that basic tabs existed, thanks for pointing this out! If we ever add an additional tabs
section to expand on the required network config on this page, they most likely would be grouped together with the above. So I'll leave them as they are for now.
When ENIs are managed by services such as NetworkManager or
systemd-networkd, it can happen that they interfere with Cilium's
configuration. For example, systemd-networkd can remove the ENI IP
assigned by Cilium if the carrier is temporarily down, thus breaking
SNAT.
We previously had a similar section regarding NetworkManager and DHCP in
the EKS installation guide, but the EKS guide has since been replaced by
the Cilium CLI installation guide.
This section here therefore acts as a replacement and states that the
devices need to be unmanaged (e.g. disabling DHCP is not enough for
systemd-networkd).