zhangyihong commented on issue #282:
URL:
https://github.com/apache/apisix-helm-chart/issues/282#issuecomment-1125614163
我尝试删除etcd 使用的pv,pvc后，再部署一次，ETCD三个pod都不再发生错误导致重启了。
具体过程如下：
1. 卸载apisix
```
helm uninstall apisix -n ingress-apisix
```
2. 删除etcd使用的pv
```
#查询etcd的pv,pvc:
kubectl get pvc,pv -n ingress-apisix |grep apisix
persistentvolumeclaim/data-apisix-etcd-0 Bound
pvc-03976dfd-a1fb-4fcd-ba14-4d4eb050d6fc 8Gi RWO gp2
23d
persistentvolumeclaim/data-apisix-etcd-1 Bound
pvc-7ba580bc-d6fa-406a-a0b8-6aaff2ba3c01 8Gi RWO gp2
23d
persistentvolumeclaim/data-apisix-etcd-2 Bound
pvc-fed68916-d3ac-4b4a-a663-c0685d0e5884 8Gi RWO gp2
23d
persistentvolume/pvc-03976dfd-a1fb-4fcd-ba14-4d4eb050d6fc 8Gi RWO
Delete Bound ingress-apisix/data-apisix-etcd-0
gp2 23d
persistentvolume/pvc-7ba580bc-d6fa-406a-a0b8-6aaff2ba3c01 8Gi RWO
Delete Bound ingress-apisix/data-apisix-etcd-1
gp2 23d
persistentvolume/pvc-fed68916-d3ac-4b4a-a663-c0685d0e5884 8Gi RWO
Delete Bound ingress-apisix/data-apisix-etcd-2
gp2 23d
#删除所有pvc(相应的pv也会删除):
kubectl delete pvc data-apisix-etcd-0 -n ingress-apisix
persistentvolumeclaim "data-apisix-etcd-0" deleted
kubectl delete pvc data-apisix-etcd-1 -n ingress-apisix
persistentvolumeclaim "data-apisix-etcd-1" deleted
kubectl delete pvc data-apisix-etcd-2 -n ingress-apisix
persistentvolumeclaim "data-apisix-etcd-2" deleted
```
3. 重写安装apisix
```
#更新repo
helm repo update
#安装
helm install apisix apisix/apisix \
--set gateway.type=LoadBalancer \
--set ingress-controller.enabled=true \
--namespace ingress-apisix \
--set
ingress-controller.config.apisix.serviceNamespace=ingress-apisix
```
4. 查询安装的版本：
发现已经有更新了 apisix-0.9.2 ---> apisix-0.9.3
```
helm list -n ingress-apisix
NAME NAMESPACE REVISION UPDATED
STATUS CHART APP VERSION
apisix ingress-apisix 1 2022-05-13 10:38:41.243799
+0800 CST deployed apisix-0.9.3 2.13.1
```
5. 检查pod的运行状态：
```
kubectl get po -n ingress-apisix
NAME READY STATUS RESTARTS AGE
apisix-8fd7755b8-fckm6 1/1 Running 0
7m56s
apisix-etcd-0 1/1 Running 0
7m56s
apisix-etcd-1 1/1 Running 0
7m56s
apisix-etcd-2 1/1 Running 0
7m56s
apisix-ingress-controller-999c5bf97-hh7mh 1/1 Running 0
7m56s
```
etcd的三个pod 都运行正常，不再发生重启！
6. 检查etcd 的成员列表也有3个了：
```
kubectl exec -it apisix-etcd-0 -n ingress-apisix -- bash
I have no name!@apisix-etcd-0:/opt/bitnami/etcd$
I have no name!@apisix-etcd-0:/opt/bitnami/etcd$ etcdctl --endpoints
"http://apisix-etcd.ingress-apisix.svc.cluster.local:2379"; member list
39e3f227d2d33a6d, started, apisix-etcd-2,
http://apisix-etcd-2.apisix-etcd-headless.ingress-apisix.svc.cluster.local:2380,
http://apisix-etcd-2.apisix-etcd-headless.ingress-apisix.svc.cluster.local:2379,http://apisix-etcd.ingress-apisix.svc.cluster.local:2379,
false
47324e080c98137d, started, apisix-etcd-1,
http://apisix-etcd-1.apisix-etcd-headless.ingress-apisix.svc.cluster.local:2380,
http://apisix-etcd-1.apisix-etcd-headless.ingress-apisix.svc.cluster.local:2379,http://apisix-etcd.ingress-apisix.svc.cluster.local:2379,
false
e2571e968b89c849, started, apisix-etcd-0,
http://apisix-etcd-0.apisix-etcd-headless.ingress-apisix.svc.cluster.local:2380,
http://apisix-etcd-0.apisix-etcd-headless.ingress-apisix.svc.cluster.local:2379,http://apisix-etcd.ingress-apisix.svc.cluster.local:2379,
false
```
7. 不清楚是切底删除etcd的pv还是升级apisix-0.9.2 ---> apisix-0.9.3后，导致问题得到解决。
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
