velero: [v1.4.0-beta.1] Unable to restore restic data with custom certificate option.

What steps did you take and what happened: I have deployed the latest beta version to use custom ca cert. The backups is performed properly with restic and I see the data in minio under mybubket/restic

But when trying to restore restic fails whit x509: certificate signed by unknown authority

What did you expect to happen: The connection should work for the restic restore as the same for the restic backup.

The output of the following commands will help us better understand what’s going on: (Pasting long output into a GitHub gist or other pastebin is fine.)

• kubectl logs deployment/velero -n velero deployment_velero.log

• velero backup describe <backupname> or kubectl get backup/<backupname> -n velero -o yaml velero_backup_describe.log

• velero backup logs <backupname> velero_backup.log

• velero restore describe <restorename> or kubectl get restore/<restorename> -n velero -o yaml velero_restore_describe.log

• velero restore logs <restorename> velero_restore.log

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Environment:

• Velero version (use velero version): Client: Version: v1.4.0-beta.1 Git commit: 8bf75bd4f28b27483ba2d7954ab61f406d8a7db5 Server: Version: v1.4.0-beta.1

• Velero features (use velero client config get features): features: <NOT SET>

• Kubernetes version (use kubectl version): Client Version: version.Info{Major:“1”, Minor:“15”, GitVersion:“v1.15.11”, GitCommit:“d94a81c724ea8e1ccc9002d89b7fe81d58f89ede”, GitTreeState:“clean”, BuildDate:“2020-03-12T21:08:59Z”, GoVersion:“go1.12.17”, Compiler:“gc”, Platform:“linux/amd64”} Server Version: version.Info{Major:“1”, Minor:“15”, GitVersion:“v1.15.11”, GitCommit:“d94a81c724ea8e1ccc9002d89b7fe81d58f89ede”, GitTreeState:“clean”, BuildDate:“2020-03-12T21:00:06Z”, GoVersion:“go1.12.17”, Compiler:“gc”, Platform:“linux/amd64”}

• Kubernetes installer & version: rke v1.0.6

• Cloud provider or hardware configuration: hardware

• OS (e.g. from /etc/os-release): kubectl get nodes -o wide NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME ltec-fil-m-01 Ready controlplane,etcd 245d v1.15.11 10.195.177.52 <none> Ubuntu 16.04.6 LTS 4.4.0-169-generic docker://18.9.9 ltec-fil-m-02 Ready controlplane,etcd 245d v1.15.11 10.195.177.53 <none> Ubuntu 16.04.6 LTS 4.4.0-169-generic docker://18.9.9 ltec-fil-m-03 Ready controlplane,etcd 245d v1.15.11 10.195.177.54 <none> Ubuntu 16.04.6 LTS 4.4.0-169-generic docker://18.9.9 ltec-fil-w-01 Ready worker 245d v1.15.11 10.195.177.55 <none> Ubuntu 16.04.6 LTS 4.4.0-169-generic docker://18.9.9 ltec-fil-w-02 Ready worker 245d v1.15.11 10.195.177.56 <none> Ubuntu 16.04.6 LTS 4.4.0-169-generic docker://18.9.9 ltec-fil-w-03 Ready worker 207d v1.15.11 10.195.177.57 <none> Ubuntu 16.04.6 LTS 4.4.0-169-generic docker://18.9.9 ltec-fil-w-99 Ready worker 121d v1.15.11 10.195.200.99 <none> Ubuntu 16.04.6 LTS 4.4.0-169-generic docker://18.9.9