docs: addresses PE-3308 and PE-3316

docs/docs-content/clusters/edge/networking/vxlan-overlay.md

@@ -36,7 +36,18 @@ The Analytics team of a manufacturing company is deploying an Edge host to their
 
 * At least one Edge host registered with your Palette account.
 * Your cluster profile must have K3s as its Kubernetes distribution. 
-* All Edge hosts must be on the same network. You may provision your own virtual network to connect Edge hosts that are on different physical networks, but all Edge hosts to be included in the cluster must be on the same network before cluster creation.
+* All Edge hosts must be on the same Layer-2 network.
+* 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.
+  ```yaml {2-6}
+  stages:
+    boot:
+        - name: "Disable UDP segmentation"
+          commands:
+            - ethtool -K INTERFACE_NAME tx-udp_tnl-segmentation off
+            - ethtool -K INTERFACE_NAME tx-udp_tnl-csum-segmentation off
+  ```
+  This is related to a [known issue with VMware's VMXNET3 adapter](https://github.com/cilium/cilium/issues/13096#issuecomment-723901955), which is widely used in different virtual machine management services, including VMware vSphere and Hyper-V. 
+
 
 ## Enable Overlay Network
 
@@ -73,16 +84,16 @@ You will not be able to change the network overlay configurations after the clus
     <Tabs>
     <TabItem value="calico" label="Calico">
 
-    In the Calico pack YAML file default template, uncomment `manifests.calico.env.calicoNode.IP_AUTODETECTION_METHOD` and set its value to `interface=scbr-100`. 
-    ```yaml {11}
+    In the Calico pack YAML file default template, uncomment `FELIX_IPV6SUPPORT` and set its value to `scbr-100` and uncomment `manifests.calico.env.calicoNode.IP_AUTODETECTION_METHOD` and set its value to `interface=scbr-100`.  
+    ```yaml {8,11}
     manifests:
         calico:
             ...
             env:
             # Additional env variables for calico-node
             calicoNode:
                 #IPV6: "autodetect"
-                #FELIX_IPV6SUPPORT: "true"
+                FELIX_IPV6SUPPORT: "scbr-100"
                 #CALICO_IPV6POOL_NAT_OUTGOING: "true"
                 #CALICO_IPV4POOL_CIDR: "192.168.0.0/16"
                 IP_AUTODETECTION_METHOD: "interface=scbr-100"
@@ -148,3 +159,9 @@ You can access a cluster with overlay network enabled in the following ways:
 - Access LoadBalancer services. You can provision LoadBalancer services in your Kubernetes cluster and expose them to external traffic. For example, refer to [Publish Cluster Services with Kube-vip](kubevip.md).
 - Access a node by IP address. You can use the node's external IP address to access the node directly. The overlay IP addresses are internal to the cluster itself and cannot be accessed from outside the cluster.
 
+
+## Resources
+
+- [Publish Cluster Services with Kube-vip](kubevip.md)
+- [Troubleshooting - Edge](../../../troubleshooting/edge.md)
+

docs/docs-content/troubleshooting/edge.md

@@ -0,0 +1,63 @@
+---
+sidebar_label: "Edge"
+title: "Edge"
+description: "Troubleshooting steps for common Edge scenarios."
+icon: ""
+hide_table_of_contents: false
+sidebar_position: 40
+tags: ["edge", "troubleshooting"]
+---
+
+The following are common scenarios that you may encounter when using Edge.
+
+## Scenario - Override or Reconfigure Read-only File System Stage
+
+If you need to override or reconfigure the read-only file system, you can do so using the following steps.
+
+## Debug Steps
+
+<br />
+
+1. Power on the Edge host.
+
+2. Press the keyboard key `E` after highlighting the menu in `grubmenu`.
+
+3. Type `rd.cos.debugrw` and press `Enter`.
+
+![The grub menu displays with the command rd.cos.debugrw typed in the terminal.](/troubleshooting_edge_grub-menu.png)
+
+4. Press `Ctrl+X` to boot the system.
+
+5. Make the required changes to the image.
+
+6. Reboot the system to resume the default read-only file system.
+
+## Scenario - Pod State Unknown After Reboot with Overlay Network Enabled
+
+On slower networks, it's possible that this is due to KubeVip leader election timeouts. To debug, you can manually adjust the values of related environment variables in the KubeVip DaemonSet with the following steps.
+
+### Debug Steps
+
+1. Ensure you can access the cluster using kubectl.  For more information, refer to [Access Cluster with CLI](../clusters/cluster-management/palette-webctl.md).
+
+2. Issue the following command:
+
+  ```shell
+  kubectl edit ds kube-vip-ds -n kube-system
+  ```
+
+3. In the `env`  of the KubeVip service, modify the environment variables to have the following corresponding values:
+
+  ```yaml {4-9}
+  env:
+    - name: vip_leaderelection
+      value: "true"
+    - name: vip_leaseduration
+      value: "30"
+    - name: vip_renewdeadline
+      value: "20"
+    - name: vip_retryperiod
+      value: "4"
+  ```
+
+4. Within a minute, the old Pods in unknown state will be terminated and Pods will come up with the updated values.

docs/docs-content/troubleshooting/troubleshooting.md

@@ -20,7 +20,7 @@ Use the following troubleshooting resources to help you address issues that may
 - [Cluster Deployment](cluster-deployment.md)
 
 
-- [Edge](edge.mdx)
+- [Edge](edge.md)
 
 
 - [Enterprise Install](enterprise-install.md)

vale/styles/Vocab/Internal/accept.txt

@@ -169,4 +169,6 @@ Simple Mail Transfer Protocol
 NIC
 autoscale
 initContainer
+ethernet
+hostname
 Entra