Srikumar Venugopal

This is happening in CSI-S3 when processes are not quitting if the unmount operation has failed for some reason. Relabelling this issue

@foofybuster thanks for your PR and it looks very useful! I I will review it but could you please sign-off your commit as it is needed for DCO condition to...

@foofybuster To help me process this PR, can you open an issue with the details of your setup and link this PR to that ? In general, the secrets are/should...

@tvanderwal-lmco Currently, we don't have a way to do this but this would be a good feature to have. Can you sketch how this would look like in terms of...

@mahi402 thanks but could you paste the logs of `csi-s3` container instead

@mahi402 I looked through your logfiles and it seems one of your csi-s3 daemons (in `logscontainer2.txt`) is not able to connect to S3 endpoint while the other (`ip-10-0-1-25.us-west-2.compute.internal`). You could...

@mahi402 csi-s3 should not make any decisions that impact transfer costs. Can you please try accessing the bucket in the cluster with aws s3 command with the same endpoints as...

@juan-sg Apologies for late reply. `kubectl delete` getting stuck after the last line means that there is a Datashim managed object still around in the cluster. What could've happened is...

@breitling apologies. I don't get notifications for discussions (but I do for issues) To answer your question, can you paste the output of this command `$ kubectl describe dataset `...

The operator was upgraded to K8s Client v0.29 and controller-runtime v0.17 (see [PR](#346)). While this works on kind installations, it fails in the CI/CD pipeline. Not able to see why...