Liveness probe failed after helm install

[LLLLimbo]

Issue description

Liveness probe failed after helm install.

Run kubectl describe pods apisix-apisix-dashboard-5d45f878bb-5zgg6 -n ingress-apisix, I gor following output:

Name:         apisix-apisix-dashboard-5d45f878bb-5zgg6
Namespace:    ingress-apisix
Priority:     0
Node:         docker-desktop/192.168.65.4
Start Time:   Tue, 06 Apr 2021 10:48:30 +0800
Labels:       app.kubernetes.io/instance=apisix
              app.kubernetes.io/name=apisix-dashboard
              pod-template-hash=5d45f878bb
Annotations:  checksum/config: f10457ec1c68f9dc5d53e5945cc17790f290ba4fdb4e712b2f2acf6ac6cda42e
Status:       Running
IP:           10.1.1.70
IPs:
  IP:           10.1.1.70
Controlled By:  ReplicaSet/apisix-apisix-dashboard-5d45f878bb
Containers:
  apisix-dashboard:
    Container ID:   docker://0341a01a43518061b458a86ef0ba026847551afa9b7e1c60f900649baa9ad1b9
    Image:          apache/apisix-dashboard:2.3
    Image ID:       docker-pullable://apache/apisix-dashboard@sha256:724796cfd0abc842ef74ed92153fd5dcd720a3c4b1b03ed0066a77cec0e66131
    Port:           9000/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Tue, 06 Apr 2021 10:50:23 +0800
    Last State:     Terminated
      Reason:       Error
      Exit Code:    2
      Started:      Tue, 06 Apr 2021 10:49:33 +0800
      Finished:     Tue, 06 Apr 2021 10:49:38 +0800
    Ready:          True
    Restart Count:  4
    Liveness:       http-get http://:http/ping delay=0s timeout=1s period=10s #success=1 #failure=3
    Readiness:      http-get http://:http/ping delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:    <none>
    Mounts:
      /usr/local/apisix-dashboard/conf/conf.yaml from apisix-dashboard-config (rw,path="conf.yaml")
      /var/run/secrets/kubernetes.io/serviceaccount from apisix-apisix-dashboard-token-qpbc2 (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  apisix-dashboard-config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      apisix-apisix-dashboard
    Optional:  false
  apisix-apisix-dashboard-token-qpbc2:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  apisix-apisix-dashboard-token-qpbc2
    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
  ----     ------     ----               ----               -------
  Normal   Scheduled  17m                default-scheduler  Successfully assigned ingress-apisix/apisix-apisix-dashboard-5d45f878bb-5zgg6 to docker-desktop
  Warning  Unhealthy  17m (x2 over 17m)  kubelet            Readiness probe failed: Get "http://10.1.1.70:9000/ping": dial tcp 10.1.1.70:9000: connect: connection refused
  Normal   Pulled     16m (x4 over 17m)  kubelet            Container image "apache/apisix-dashboard:2.3" already present on machine
  Normal   Created    16m (x4 over 17m)  kubelet            Created container apisix-dashboard
  Normal   Started    16m (x4 over 17m)  kubelet            Started container apisix-dashboard
  Warning  Unhealthy  16m (x2 over 17m)  kubelet            Liveness probe failed: Get "http://10.1.1.70:9000/ping": dial tcp 10.1.1.70:9000: connect: connection refused
  Warning  BackOff    16m (x9 over 17m)  kubelet            Back-off restarting failed container

Expected behavior

Liveness probe succeeds.

How to Reproduce

1.helm repo add bitnami https://charts.bitnami.com/bitnami 2.helm repo add apisix https://charts.apiseven.com 3.helm repo update 4.

helm install apisix apisix/apisix 
--set allow.ipList="{0.0.0.0/0}" 
--namespace ingress-apisix

5. kubectl describe pods apisix-apisix-dashboard-5d45f878bb-5zgg6 -n ingress-apisix

Environment

• apisix version (cmd: apisix version): 2.3
• OS (cmd: uname -a): Windows 10 Home
• OpenResty / Nginx version (cmd: nginx -V or openresty -V):
• etcd version, if have (cmd: run curl http://127.0.0.1:9090/v1/server_info to get the info from server-info API):
• apisix-dashboard version, if have: 2.3
• Browser version, if have:

Additional context

PS C:\Users\Limbo> kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.7", GitCommit:"1dd5338295409edcfff11505e7bb246f0d325d15", GitTreeState:"clean", BuildDate:"2021-01-13T13:23:52Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:41:49Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}

PS C:\Users\Limbo> kubectl get svc -n ingress-apisix
NAME                      TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)             AGE
apisix-admin              ClusterIP   10.109.116.93    <none>        9180/TCP            39m
apisix-apisix-dashboard   ClusterIP   10.100.179.190   <none>        80/TCP              39m
apisix-etcd               ClusterIP   10.108.91.193    <none>        2379/TCP,2380/TCP   39m
apisix-etcd-headless      ClusterIP   None             <none>        2379/TCP,2380/TCP   39m
apisix-gateway            NodePort    10.107.22.106    <none>        80:31333/TCP        39m

[Firstsawyou]

@tokers @gxthrj If you are free, please have a look. By the way, this issue should be submitted to https://github.com/apache/apisix-helm-chart/issues. ^ _ ^

[LLLLimbo]

@tokers @gxthrj If you are free, please have a look. By the way, this issue should be submitted to https://github.com/apache/apisix-helm-chart/issues. ^ _ ^

Should I create an issue there too?

[juzhiyuan]

I will help to to transfer it.