如果使用 helm 重复部署之前没有用 helm 部署过的组件，比如 kubeovn， 会出现
Error: INSTALLATION FAILED: Unable to continue with install: ServiceAccount "ovn" in namespace "kube-system" exists and cannot be imported into the current release: invalid ownership metadata;
Error: INSTALLATION FAILED: Unable to continue with install: ServiceAccount "ovn" in namespace "kube-system" exists and cannot be imported into the current release: invalid ownership metadata;
label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm";
annotation validation error: missing key "meta.helm.sh/release-name": must be set to "kubeovn";
annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "default"
make: *** [kind-install-chart] Error 1
如果是单纯 重复部署
(vv) ➜ kube-ovn git:(fix-upgrade) make kind-init-ha-ipv4
kind delete cluster --name=kube-ovn
Deleting cluster "kube-ovn" ...
jinjanate yamls/kind.yaml.j2 -o yamls/kind.yaml
jinjanate 24.1.0, Jinja2 3.1.2
kind create cluster --config yamls/kind.yaml --name kube-ovn
ERROR: failed to create cluster: [invalid pod subnet only one CIDR allowed for single-stack networking, invalid service subnet only one CIDR allowed for single-stack networking]
make[1]: *** [kind-create] Error 1
make: *** [kind-init-ha-ipv4] Error 2
(vv) ➜ kube-ovn git:(fix-upgrade)
(vv) ➜ kube-ovn git:(fix-upgrade)
(vv) ➜ kube-ovn git:(fix-upgrade) make clean
rm -f dist/images/kube-ovn dist/images/kube-ovn-cmd
rm -f yamls/kind.yaml
rm -f yamls/clab-bgp.yaml yamls/clab-bgp-ha.yaml
rm -f ovn.yaml kube-ovn.yaml kube-ovn-crd.yaml
rm -f ovn-ic-config.yaml ovn-ic-0.yaml ovn-ic-1.yaml
rm -f kwok-node.yaml metallb-cr.yaml
rm -f cacert.pem ovn-req.pem ovn-cert.pem ovn-privkey.pem
rm -f kube-ovn.tar kube-ovn-dpdk.tar vpc-nat-gateway.tar image-amd64.tar image-amd64-dpdk.tar image-arm64.tar
rm -f kubectl-ko-log.tar.gz
rm -f -r kubectl-ko-log/
