You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using openyurt.io to manage edge nodes in our cluster. These edge nodes are small IoT devices like Raspberry PI that could reboot or be offline any time. In cases when the device reboots and is offline in order to maintain the containers on the edge flannel needs to be started with the same MAC address. We are using VXLAN.
Expected Behavior
I propose a command line argument called persistent-mac that reads the nodes annotations where the MAC address is stored. Instead of creating a random MAC address, it re-uses the one read from the node annotations.
See https://openyurt.io/docs/user-manuals/network/edge-pod-network#background for further reference.
Current Behavior
The current behavior re-generates a new MAC address on startup. This can be problematic for other nodes that want to reach the rebooted node.
Possible Solution
Like said, a flag that enables the reading of the nodes annotations to reinitialize with the known MAC address.
The text was updated successfully, but these errors were encountered:
We are using openyurt.io to manage edge nodes in our cluster. These edge nodes are small IoT devices like Raspberry PI that could reboot or be offline any time. In cases when the device reboots and is offline in order to maintain the containers on the edge flannel needs to be started with the same MAC address. We are using VXLAN.
Expected Behavior
I propose a command line argument called
persistent-mac
that reads the nodes annotations where the MAC address is stored. Instead of creating a random MAC address, it re-uses the one read from the node annotations.See https://openyurt.io/docs/user-manuals/network/edge-pod-network#background for further reference.
Current Behavior
The current behavior re-generates a new MAC address on startup. This can be problematic for other nodes that want to reach the rebooted node.
Possible Solution
Like said, a flag that enables the reading of the nodes annotations to reinitialize with the known MAC address.
The text was updated successfully, but these errors were encountered: