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
Due to the absence of the Network Manager component that enable the auto-discovery among FLUIDOS Nodes, we need to setup some parameters manually to allow Nodes discovery.
100
-
101
105
Here, the meaning of the various parameters:
102
106
103
-
- LOCAL_K8S_CLUSTER_CP_IP: The IP address of your local Kubernetes cluster Control Plane
104
-
- LOCAL_REAR_PORT: The port on which your local cluster uses the REAR protocol
105
-
- REMOTE_K8S_CLUSTER_CP_IP: It's the IP address of the remote Kubernetes cluster to which you want to negotiate Flavors thorugh REAR with.
106
-
- REMOTE_REAR_PORT: It's the port on which the remote cluster uses the REAR protocol.
107
+
- FLUIDOS_VERSION: The FLUIDOS Node version to be installed
108
+
- NODE_IP: The IP address of your local Kubernetes cluster Control Plane
109
+
- REAR_PORT: The port on which your local cluster uses the REAR protocol
110
+
- ENABLE_LOCAL_DISCOVERY: A flag that enables the Network Manager, which is the component advertising the local FLUIDOS Node into a LAN
111
+
- THIRD_OCTET: This is the third byte of the IP address used by Multus CNI for sending broadcast messages into the LAN. **Warning**: this parameters should be different for each FLUIDOS Node to be working (e.g. 1 for the 1st cluster, 2 for the 2nd cluster, etc.)
112
+
- NET_INTERFACE: The host network interface that Multus binds to
0 commit comments