Ref: https://github.com/harvester/harvester/issues/1521
Verify Items
- Agent Node should keep connection when any master Node is down
Case: Agent Node’s connecting status
- Install Harvester with 4 nodes which joining node MUST join by VIP (point
server-url
to use VIP) - Make sure all nodes are ready
- Login to dashboard, check host state become
Active
- SSH to the 1st node, run command
kubectl get node
to check all STATUS should beReady
- Login to dashboard, check host state become
- SSH to agent nodes which ROLES IS
<none>
in Step 2i’s output- Output should contains VIP in the server URL, by run command
cat /etc/rancher/rke2/config.yaml.d/90-harvester-vip.yaml
- Output should contain the line
server: https://127.0.0.1:6443
, by run commandcat /var/lib/rancher/rke2/agent/kubelet.kubeconfig
- Output should contain the line
server: https://127.0.0.1:6443
, by run commandcat /var/lib/rancher/rke2/agent/kubeproxy.kubeconfig
- Output should contains VIP in the server URL, by run command
- SSH to server nodes which ROLES contains
control-plane
in Step 2i’s output- Check file should not exist in the path
/etc/rancher/rke2/config.yaml.d/90-harvester-vip.yaml
- Check file should not exist in the path
- Shut down a server node, check following things
- Host State should not be
Active
in dashboard - Node STATUS should be
NotReady
in the command output ofkubectl get node
- STATUS of agent nodes should be
Ready
in the command output ofkubectl get node
- Host State should not be
- Power on the server node, wait until it back to cluster
- repeat Step 5-6 for other server nodes