skip NetworkManager unmanagement operations for bond devices automatically

[qiutingjun]

• Make sure you have followed Kube-OVN Code Style.

What type of this PR

• Features
• Bug fixes

set the nic could be managed by NetworkManager or not

Which issue(s) this PR fixes:

Fixes #2983

WHAT

🤖 Generated by Copilot at c8374a2

This pull request adds a new flag --manage-nic-by-network-manager to the ovn-cni container and a corresponding Helm value MANAGE-NIC-BY-NETWORK-MANAGER to the charts, which allow users to configure whether the ovn-cni plugin should set the network interface link managed by NetworkManager or not. This feature is intended to address the issue #1409, where some users reported network connectivity problems caused by NetworkManager interference.

🤖 Generated by Copilot at c8374a2

To fix an issue with NetworkManager
We added a flag to the ovn-cni container
It sets the link managed or not
Based on the config field we got
And we hope it makes the network smoother

HOW

🤖 Generated by Copilot at c8374a2

• Add a new flag --manage-nic-by-network-manager to the ovn-cni container arguments to allow users to configure NetworkManager management of network interface links (link)
• Add a new Helm value MANAGE-NIC-BY-NETWORK-MANAGER to the networking section in values.yaml to customize the flag value (link)
• Add a new field ManageNicByNetworkManager to the Configuration struct to store the flag value (link)
• Parse the flag value from the command-line arguments using the pflag package and assign it to the configuration field (link, link)
• Modify the calls to the SetManaged method of the nmSyncer object in changeProvideNicName and transferAddrsAndRoutes functions to pass the configuration field as the second argument, making the ovn-cni plugin respect the user's choice of NetworkManager management (link, link)

[bobz965]

@zhangzujian hi, there is a problem when using NetworkManager to manage bond, if set NetworkManager to be false, will cause binding nic's vlan subnic status to down. could you help review this?

[zhangzujian]

@zhangzujian hi, there is a problem when using NetworkManager to manage bond, if set NetworkManager to be false, will cause binding nics split into two nics. could you help review this?

We can skip NetworkManager operations for bond devices automatically, instead of adding an option to kube-ovn-cni.

[qiutingjun]

@zhangzujian hi, there is a problem when using NetworkManager to manage bond, if set NetworkManager to be false, will cause binding nics split into two nics. could you help review this?

We can skip NetworkManager operations for bond devices automatically, instead of adding an option to kube-ovn-cni.

solution changed

[oilbeater]

We need further consider this, other networkmanager config like sub interface may also hit the same issue.