PhanLe1010

@brunosmartin Could you give the output of `top` or `cat /proc//status` after applying the workaround?

I will have sample report to demonstrate the use case for this PR in more detailed

For example, this is a test run on a cluster of 3 worker nodes. Each has 4CPUs, 8GiB of RAM. with the test parameters: * Longhorn RWO volumes: each Kbench...

We are building Longhorn report using this PR https://github.com/longhorn/longhorn/pull/7905

Thanks all! I will create the PR into the new Longhorn repo

This PR is ready for review cc @derekbit @shuo-wu @ejweber @james-munson For the todo items: I will modify the document and upgrade Golang version tomorrow

> For the todo items: I will modify the document and upgrade Golang version tomorrow I will open a new PR for this

> Rather, we should refine the check that already exists in kubernetes_pod_controller, and skip the workload restart if > - `auto-delete-pod-when-volume-detached-unexpectedly` is false, OR > - if the volume that...

> Although this necessary for reliable fast failover, it can also be used to control when the pod is considered ready, since the readiness probe uses the webhook to answer...

Yeah, I think I hit this one one time in the past out of many tests. I agree that it is ok to move this ticket to v1.8.0 because: 1....