huangzx3 opened a new issue #198:
URL: https://github.com/apache/apisix-helm-chart/issues/198
```
Name: apisix-1640071150-etcd-0
Namespace: default
Priority: 0
Node: izbp17djxylxntd8nigwg0z/172.16.219.233
Start Time: Tue, 21 Dec 2021 16:06:54 +0800
Labels: app.kubernetes.io/instance=apisix-1640071150
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=etcd
controller-revision-hash=apisix-1640071150-etcd-5f57bcbf6
helm.sh/chart=etcd-6.2.6
statefulset.kubernetes.io/pod-name=apisix-1640071150-etcd-0
Annotations: cni.projectcalico.org/podIP: 100.79.164.131/32
Status: Running
IP: 100.79.164.131
IPs:
IP: 100.79.164.131
Controlled By: StatefulSet/apisix-1640071150-etcd
Containers:
etcd:
Container ID:
containerd://3e08a916be53b5fcff17c0b7ef41679116e3f9176cf9c14e8f0653cedd579e0f
Image: docker.io/bitnami/etcd:3.4.16-debian-10-r14
Image ID:
docker.io/bitnami/etcd@sha256:ef2d499749c634588f7d281dd70cc1fb2514d57f6d42308c0fb0f2c8ca55bea4
Ports: 2379/TCP, 2380/TCP
Host Ports: 0/TCP, 0/TCP
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Tue, 21 Dec 2021 17:19:42 +0800
Finished: Tue, 21 Dec 2021 17:19:42 +0800
Ready: False
Restart Count: 19
Liveness: exec [/opt/bitnami/scripts/etcd/healthcheck.sh]
delay=60s timeout=5s period=30s #success=1 #failure=5
Readiness: exec [/opt/bitnami/scripts/etcd/healthcheck.sh]
delay=60s timeout=5s period=10s #success=1 #failure=5
Environment:
BITNAMI_DEBUG: false
MY_POD_IP: (v1:status.podIP)
MY_POD_NAME: apisix-1640071150-etcd-0
(v1:metadata.name)
ETCDCTL_API: 3
ETCD_ON_K8S: yes
ETCD_START_FROM_SNAPSHOT: no
ETCD_DISASTER_RECOVERY: no
ETCD_NAME: $(MY_POD_NAME)
ETCD_DATA_DIR: /bitnami/etcd/data
ETCD_LOG_LEVEL: info
ALLOW_NONE_AUTHENTICATION: yes
ETCD_ADVERTISE_CLIENT_URLS:
http://$(MY_POD_NAME).apisix-1640071150-etcd-headless.default.svc.cluster.local:2379
ETCD_LISTEN_CLIENT_URLS: http://0.0.0.0:2379
ETCD_INITIAL_ADVERTISE_PEER_URLS:
http://$(MY_POD_NAME).apisix-1640071150-etcd-headless.default.svc.cluster.local:2380
ETCD_LISTEN_PEER_URLS: http://0.0.0.0:2380
ETCD_INITIAL_CLUSTER_TOKEN: etcd-cluster-k8s
ETCD_INITIAL_CLUSTER_STATE: new
ETCD_INITIAL_CLUSTER:
apisix-1640071150-etcd-0=http://apisix-1640071150-etcd-0.apisix-1640071150-etcd-headless.default.svc.cluster.local:2380,apisix-1640071150-etcd-1=http://apisix-1640071150-etcd-1.apisix-1640071150-etcd-headless.default.svc.cluster.local:2380,apisix-1640071150-etcd-2=http://apisix-1640071150-etcd-2.apisix-1640071150-etcd-headless.default.svc.cluster.local:2380
ETCD_CLUSTER_DOMAIN:
apisix-1640071150-etcd-headless.default.svc.cluster.local
Mounts:
/bitnami/etcd from data (rw)
/var/run/secrets/kubernetes.io/serviceaccount from default-token-kt7g4
(ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
data:
Type: PersistentVolumeClaim (a reference to a
PersistentVolumeClaim in the same namespace)
ClaimName: data-apisix-1640071150-etcd-0
ReadOnly: false
default-token-kt7g4:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-kt7g4
Optional: false
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning BackOff 3m51s (x333 over 73m) kubelet Back-off restarting
failed container
```
3 etcd pods running , but always Back-off restarting failed container .
please help
--
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]
