From 3883aebab7a375802d50e215965ab58336e7a48b Mon Sep 17 00:00:00 2001 From: antongisli Date: Wed, 19 Jun 2024 01:23:17 +0530 Subject: [PATCH 1/2] Update vxlan-overlay.md add more info about allowing broadcast messages between edge hosts. we might consider making this a warning to ensure it is seen and attention paid to it. --- docs/docs-content/clusters/edge/networking/vxlan-overlay.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/docs-content/clusters/edge/networking/vxlan-overlay.md b/docs/docs-content/clusters/edge/networking/vxlan-overlay.md index c815e61cf0..3f3156ce9f 100644 --- a/docs/docs-content/clusters/edge/networking/vxlan-overlay.md +++ b/docs/docs-content/clusters/edge/networking/vxlan-overlay.md @@ -58,6 +58,9 @@ server. The region experiences a bad weather event that causes a sustained outag - At least one Edge host registered with your Palette account. - Your cluster profile must have K3s or RKE2 as its Kubernetes distribution. - All Edge hosts must be on the same Layer-2 network. + - Broadcast messages must be allowed between all Edge hosts participating in the cluster. + - Features such as promiscuous mode for VM hosts on VMware must be enabled to allow broadcasts between hosts. + - Switches must not implement features that block broadcast between ports where Edge hosts are connected. - If you are launching your Edge hosts in virtual machine environments and you are using either Cilium or Flannel as your container network interface (CNI), ensure that you add the following commands in the **user-data** file at the boot stage. Replace `INTERFACE_NAME` with the name of the network interface on your Edge host. From 329d39514b74e8d6c7268c2341bbad9b090b9f2b Mon Sep 17 00:00:00 2001 From: Lenny Chen Date: Tue, 18 Jun 2024 15:33:05 -0700 Subject: [PATCH 2/2] docs: slight copy edit --- .../docs-content/clusters/edge/networking/vxlan-overlay.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/docs-content/clusters/edge/networking/vxlan-overlay.md b/docs/docs-content/clusters/edge/networking/vxlan-overlay.md index 3f3156ce9f..821cc5a1e1 100644 --- a/docs/docs-content/clusters/edge/networking/vxlan-overlay.md +++ b/docs/docs-content/clusters/edge/networking/vxlan-overlay.md @@ -58,9 +58,10 @@ server. The region experiences a bad weather event that causes a sustained outag - At least one Edge host registered with your Palette account. - Your cluster profile must have K3s or RKE2 as its Kubernetes distribution. - All Edge hosts must be on the same Layer-2 network. - - Broadcast messages must be allowed between all Edge hosts participating in the cluster. - - Features such as promiscuous mode for VM hosts on VMware must be enabled to allow broadcasts between hosts. - - Switches must not implement features that block broadcast between ports where Edge hosts are connected. +- Broadcast messages must be allowed between all Edge hosts participating in the cluster. + - For Virtual Machine (VM) Edge hosts in VMware, this means features such as promiscuous mode must be enabled to allow + broadcasts between hosts. + - Switches cannot implement features that block broadcast between ports where Edge hosts are connected. - If you are launching your Edge hosts in virtual machine environments and you are using either Cilium or Flannel as your container network interface (CNI), ensure that you add the following commands in the **user-data** file at the boot stage. Replace `INTERFACE_NAME` with the name of the network interface on your Edge host.