kube-ovn bug 待测试

kube-ovn升级步骤:https://github.com/kubeovn/kube-ovn/issues/5566

  1. https://github.com/kubeovn/kube-ovn/issues/4506

  2. DB恢复 https://github.com/kubeovn/kube-ovn/issues/1805

经过讨论,确认 OVN SB DB的恢复,由 ovs-ovn的健康检查,自动执行 sb-cluster-state-reset 命令实现。
NB DB 的恢复,在重启 ovn-central pod 之后,通过删除 kube-ovn-controller pod 重建,利用 kube-ovn-controller 的初始化来恢复。

  1. pod分配不到IP地址

https://github.com/kubeovn/kube-ovn/issues/5125 还没有解决, 相关已经解决的有:

https://github.com/kubeovn/kube-ovn/issues/2186
https://github.com/kubeovn/kube-ovn/pull/2432

https://github.com/kubeovn/kube-ovn/issues/5125 说是 在1.14 版本上已经解决,可以升级看一下。


#!/bin/bash

echo "Notice: must run this script on target node" 
echo "refer:https://kubeovn.github.io/docs/v1.14.x/ops/delete-worker-node/"


nodeName=$(hostname)

kubectl drain $nodeName  --ignore-daemonsets --force

crictl rm -f $(crictl ps | grep openvswitch | awk '{print $1}')

systemctl stop kubelet

rm -rf /var/run/openvswitch
rm -rf /var/run/ovn
rm -rf /etc/origin/openvswitch/
rm -rf /etc/origin/ovn/
rm -rf /etc/cni/net.d/00-kube-ovn.conflist
rm -rf /etc/cni/net.d/01-kube-ovn.conflist
rm -rf /var/log/openvswitch
rm -rf /var/log/ovn

kubectl delete node $nodeName 

kubectl ko sbctl show |grep -B 2 $nodeName   > /tmp/sb.txt
kubectl ko sbctl show |grep -A 10 $nodeName   >> /tmp/sb.txt

chassis_id=$(grep Chassis /tmp/sb.txt | awk '{print $2}') 

if [ -z $chassis_id ]; then 
   kubectl ko sbctl chassis-del  $chassis_id 
else
   echo "the $nodeName no left db in south db."
fi 
posted @ 2025-08-07 06:57  todaygood  阅读(25)  评论(0)    收藏  举报