Nick

Thanks for the provided workaround. We are also hitting this bug from time to time. I tried the parallelism approach and did not see the 'localhost issue' again. However, we...

Interesting @igoooor , does it also try to connect to localhost in your case? We have a similiar issue, like the one you describe, but in those cases we just...

Yeah, this might be the case. In most of our cases we are not using terraform data sources to fill in the access credentials, but we are still experiencing this...

Hi there, we are facing the same issue. In our case velero is the only application which creates volumesnapshots. We do have schedules which overlap in terms of times and...

Hi there, is there any news on this issue? We also would like to use the 'official' client here, but have the same concerns.

I was actually wondering about the same thing, but when looking at the command which gets executed ("wait-shutdown") and looking at the [corresponding code](https://github.com/kubernetes/ingress-nginx/blob/293071ae024adfecd2fc3499c52aa54f968e935e/cmd/waitshutdown/main.go#L29), I noticed that still a SIGTERM...

Thank you very much for the information. This means that zero downtime deployments are already implemented, right?

Hi, is there something we could do here to fix this issue? I like the suggestion from https://github.com/vmware-tanzu/velero/issues/5781#issuecomment-1387125381 to ignore non existing items.

In our case we are just using the [csi plugin](https://github.com/vmware-tanzu/velero-plugin-for-csi) to create Kubernetes Snapshots of PVC content. Velero is the sole creator/manager of all backups. Maybe @draghuram , for the...

@draghuram There is no other component running in the cluster which would take care of backups or snapshots. Velero is the only component which takes care of it. Except you...