Skip to main content
Version: latest

Edge

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


  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.

  1. Press Ctrl+X to boot the system.

  2. Make the required changes to the image.

  3. 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.

  2. Issue the following command:

kubectl edit ds kube-vip-ds -n kube-system
  1. In the env of the KubeVip service, modify the environment variables to have the following corresponding values:
env:
- name: vip_leaderelection
value: "true"
- name: vip_leaseduration
value: "30"
- name: vip_renewdeadline
value: "20"
- name: vip_retryperiod
value: "4"
  1. Within a minute, the old Pods in unknown state will be terminated and Pods will come up with the updated values.