whichdew opened a new issue, #7446:
URL: https://github.com/apache/apisix/issues/7446

   ### Current Behavior
   
   
   
![image](https://user-images.githubusercontent.com/20438962/178460531-c74067b7-b261-4eb0-bde3-194d0715efa0.png)
   
   ```
    Warning  Unhealthy         8m50s (x3 over 9m50s)  kubelet            
Liveness probe failed: command "/opt/bitnami/scripts/etcd/healthcheck.sh" timed 
out
     Warning  Unhealthy         8m22s                  kubelet            
Readiness probe failed:
     Warning  Unhealthy         8m22s                  kubelet            
Liveness probe failed:
     Normal   Created           8m21s (x2 over 10m)    kubelet            
Created container etcd
     Normal   Started           8m21s (x2 over 10m)    kubelet            
Started container etcd
     Normal   Pulled            8m21s (x2 over 10m)    kubelet            
Container image "docker.io/bitnami/etcd:3.4.18-debian-10-r14" already present 
on machine
     Warning  Unhealthy         40s (x34 over 9m50s)   kubelet            
Readiness probe failed: command "/opt/bitnami/scripts/etcd/healthcheck.sh" 
timed out
   ```
   As you can see, etcd and dashboard can't start
   
   ### Expected Behavior
   
   _No response_
   
   ### Error Logs
   
   _No response_
   
   ### Steps to Reproduce
   
   1. kubeadm 1.24.2 
   2. create pv without storageClassName
   3. helm install apisix apisix -n apisix
   
   ### Environment
   
   - APISIX version (run `apisix version`):
   - Operating system (run `uname -a`):
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`):
   - etcd version, if relevant (run `curl 
http://127.0.0.1:9090/v1/server_info`):
   - APISIX Dashboard version, if relevant:
   - Plugin runner version, for issues related to plugin runners:
   - LuaRocks version, for installation issues (run `luarocks --version`):
   


-- 
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]

Reply via email to