From 946f42e83cdf020f0f562070514c548bf4da70c5 Mon Sep 17 00:00:00 2001 From: antongisli Date: Wed, 19 Jun 2024 00:44:23 +0200 Subject: [PATCH] docs: update vxlan-overlay.md (#3121) * 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: slight copy edit --------- Co-authored-by: Lenny Chen Co-authored-by: Lenny Chen <55669665+lennessyy@users.noreply.github.com> (cherry picked from commit 73c5d0d9fa368d0a4812e322fc01344dc36a00fc) --- docs/docs-content/clusters/edge/networking/vxlan-overlay.md | 4 ++++ 1 file changed, 4 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..821cc5a1e1 100644 --- a/docs/docs-content/clusters/edge/networking/vxlan-overlay.md +++ b/docs/docs-content/clusters/edge/networking/vxlan-overlay.md @@ -58,6 +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. + - 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.