JohnnyQianP opened a new issue, #272:
URL: https://github.com/apache/apisix-helm-chart/issues/272

   
![image](https://user-images.githubusercontent.com/14548092/164751511-d7d1bc9f-1122-47a7-befd-abb443e404ab.png)
   ```
   # kubectl get pods -n ingress-apisix
   NAME                         READY   STATUS     RESTARTS   AGE
   my-apisix-5fbc74568f-6pps2   0/1     Init:0/1   0          26m
   my-apisix-etcd-0             0/1     Pending    0          50m
   my-apisix-etcd-1             0/1     Pending    0          50m
   my-apisix-etcd-2             0/1     Pending    0          25m
   
   # kubectl describe pod my-apisix-etcd-0 -n ingress-apisix
   Name:           my-apisix-etcd-0
   Namespace:      ingress-apisix
   Priority:       0
   Node:           <none>
   Labels:         app.kubernetes.io/instance=my-apisix
                   app.kubernetes.io/managed-by=Helm
                   app.kubernetes.io/name=etcd
                   controller-revision-hash=my-apisix-etcd-5b96d6bfb4
                   helm.sh/chart=etcd-7.0.4
                   statefulset.kubernetes.io/pod-name=my-apisix-etcd-0
   Annotations:    checksum/token-secret: 
971aed8b8aa5756f775f81a27b2e5d07dae029e5ed787033e6703db5be62b008
   Status:         Pending
   IP:             
   IPs:            <none>
   Controlled By:  StatefulSet/my-apisix-etcd
   Containers:
     etcd:
       Image:       docker.io/bitnami/etcd:3.4.18-debian-10-r14
       Ports:       2379/TCP, 2380/TCP
       Host Ports:  0/TCP, 0/TCP
       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:                       my-apisix-etcd-0 (v1:metadata.name)
         MY_STS_NAME:                       my-apisix-etcd
         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_AUTH_TOKEN:                   
jwt,priv-key=/opt/bitnami/etcd/certs/token/jwt-token.pem,sign-method=RS256,ttl=10m
         ETCD_ADVERTISE_CLIENT_URLS:        
http://$(MY_POD_NAME).my-apisix-etcd-headless.ingress-apisix.svc.cluster.local:2379,http://my-apisix-etcd.ingress-apisix.svc.cluster.local:2379
         ETCD_LISTEN_CLIENT_URLS:           http://0.0.0.0:2379
         ETCD_INITIAL_ADVERTISE_PEER_URLS:  
http://$(MY_POD_NAME).my-apisix-etcd-headless.ingress-apisix.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:              
my-apisix-etcd-0=http://my-apisix-etcd-0.my-apisix-etcd-headless.ingress-apisix.svc.cluster.local:2380,my-apisix-etcd-1=http://my-apisix-etcd-1.my-apisix-etcd-headless.ingress-apisix.svc.cluster.local:2380,my-apisix-etcd-2=http://my-apisix-etcd-2.my-apisix-etcd-headless.ingress-apisix.svc.cluster.local:2380
         ETCD_CLUSTER_DOMAIN:               
my-apisix-etcd-headless.ingress-apisix.svc.cluster.local
       Mounts:
         /bitnami/etcd from data (rw)
         /opt/bitnami/etcd/certs/token/ from etcd-jwt-token (ro)
         /var/run/secrets/kubernetes.io/serviceaccount from default-token-2756j 
(ro)
   Conditions:
     Type           Status
     PodScheduled   False 
   Volumes:
     data:
       Type:       PersistentVolumeClaim (a reference to a 
PersistentVolumeClaim in the same namespace)
       ClaimName:  data-my-apisix-etcd-0
       ReadOnly:   false
     etcd-jwt-token:
       Type:        Secret (a volume populated by a Secret)
       SecretName:  my-apisix-etcd-jwt-token
       Optional:    false
     default-token-2756j:
       Type:        Secret (a volume populated by a Secret)
       SecretName:  default-token-2756j
       Optional:    false
   QoS Class:       BestEffort
   Node-Selectors:  <none>
   Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                    node.kubernetes.io/unreachable:NoExecute for 300s
   Events:
     Type     Reason            Age        From               Message
     ----     ------            ----       ----               -------
     Warning  FailedScheduling  <unknown>  default-scheduler  Failed to bind 
volumes: timed out waiting for the condition
     Warning  FailedScheduling  <unknown>  default-scheduler  Failed to bind 
volumes: timed out waiting for the condition
     Warning  FailedScheduling  <unknown>  default-scheduler  Failed to bind 
volumes: timed out waiting for the condition
     Warning  FailedScheduling  <unknown>  default-scheduler  Failed to bind 
volumes: timed out waiting for the condition
   ```
   
   Any ideas? Please help to find the solution. I guess it's related with etcd, 
but I don't know the details.
   
   Below, apisix is installed
   
   # helm3 list -n ingress-apisix
   NAME         NAMESPACE       REVISION        UPDATED                         
        STATUS          CHART           APP VERSION
   my-apisix    ingress-apisix  1               2022-04-22 22:48:08.038264423 
+0800 CST deployed        apisix-0.9.1    2.13.1 
   


-- 
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: notifications-unsubscr...@apisix.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to