You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I have installed velero (v1.9) and the local-volume-provider (0.3.3) in my k8s cluster. I am able to do backups and restores successfully. But I have some issues when I am checking logs or backup details. For example: $ velero backup logs backup-41 An error occurred: Get "http://172.29.3.166:3000/nfs-snapshots/backups/backup-41/backup-41-logs.gz?expires=2022-07-27T15%3A22%3A58.124Z&signature=KCvo8QFpUqtp_QlIbQZB03_dbLA=": dial tcp 172.29.3.166:3000: connect: connection refused
The URLs mentioned in the error message work from a pod within the k8s cluster but not from the velero client. The error is raised by the local-volume-provider sidecar.
Did someone already encounter the same issue ?
Let me know if you need more input.
Thank you.
The text was updated successfully, but these errors were encountered:
Hi,
I have installed velero (v1.9) and the local-volume-provider (0.3.3) in my k8s cluster. I am able to do backups and restores successfully. But I have some issues when I am checking logs or backup details. For example:
$ velero backup logs backup-41 An error occurred: Get "http://172.29.3.166:3000/nfs-snapshots/backups/backup-41/backup-41-logs.gz?expires=2022-07-27T15%3A22%3A58.124Z&signature=KCvo8QFpUqtp_QlIbQZB03_dbLA=": dial tcp 172.29.3.166:3000: connect: connection refused
$ velero backup describe backup-41 --details ... Resource List: <error getting backup resource list: Get "http://172.29.3.166:3000/nfs-snapshots/backups/backup-41/backup-41-resource-list.json.gz?expires=2022-07-27T15%3A24%3A39.114Z&signature=JyObtPAybGAXCH1_uJSf8XVMa48=": dial tcp 172.29.3.166:3000: connect: connection refused>
The URLs mentioned in the error message work from a pod within the k8s cluster but not from the velero client. The error is raised by the local-volume-provider sidecar.
Did someone already encounter the same issue ?
Let me know if you need more input.
Thank you.
The text was updated successfully, but these errors were encountered: