dyrnq
> Hi, I'm not sure why you experience this bug, I checked it myself and didn't reproduce it I think logs from csi-s3 containers could help... please attach them? :-)...
@vitalif this is my test case [test-csi-s3.sh.md](https://github.com/yandex-cloud/k8s-csi-s3/files/15094698/test-csi-s3.sh.md) ```bash kubectl logs -l app=csi-s3 -c csi-s3 -n kube-system ``` [csi-s3.log](https://github.com/yandex-cloud/k8s-csi-s3/files/15095058/csi-s3.log)
Finally I found a solution, which can be solvedusing the following `startupProbe` and `terminationGracePeriodSeconds: 2` for **quick fail** ```bash #livenessProbe: startupProbe: exec: command: - ls - /usr/share/nginx/html/s3 initialDelaySeconds: 2 periodSeconds:...
@wfy-belief 你可以使用 ApisixUpstream 的 healthCheck.active 主动健康检测9870端口的 /isActive 路径，这个在haproxy中很好实现 可以参考
@pablobm hello,whitch distribution linux are you using. as says `Zed requires a Vulkan 1.3 driver` I use debian12 and CPU is `Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz` if you are...
@jluncc Hi, have you found a solution?