[BUG]backup repo pre-check faild

[StanleyWang-GitHub]

• Environment：K8S-v1.28.15
• kubeblock：v1.0.0
• s3-compatible provider: ceph-rgw

---

Hi @shanshanying ，
I found kbcli create backup repo has problem with s3-compatible provider.
have tried following:

#kbcli backuprepo create s3-backuprepo --provider=s3-compatible --access-key-id=xxx --bucket=kubeblocks --endpoint=https://s3.stanley.wang --secret-access-key=xxx --force-path-style=true --insecure-skip-tls-verify=true
and
#kbcli backuprepo create s3-backuprepo --provider=s3-compatible --access-key-id=xxx --bucket=kubeblocks --endpoint=https://s3.stanley.wang --secret-access-key=xxx --force-path-style=true --insecure=true

The pre-check job failed with:

Error: push to "/precheck.txt": RequestError: send request failed
caused by: Put"https://s3.stanley.wang/kubeblocks": tls:failed to verify certificate: x509: certificate signed by unknown authority

BTW the tls certificate is self signed.

I've tried the same storage in http protocol and the pre-check successed.

Therefor I strongly believe that kbcli backuprepo create --insecure and --insecure-skip-tls-verify options didn't take effect at all.

Looking forward to your further reply.

Regards.

[shanshanying]

@zjx20 could you please help on this issue.

[zjx20]

Hi @StanleyWang-GitHub, thanks for your feedback. You might be right, the --insecure option doesn't seem to be taking effect. This is because the option isn't being correctly set for the underlying rclone. However, there's no simple workaround at the moment. We will evaluate how to fix it.

[zjx20]

@StanleyWang-GitHub This issue has been fixed in apecloud/datasafed#17, and the new datasafed image has also been packaged (tagged 0.2.1).

Now, you can use this version by specifying the helm parameter --set dataProtection.image.datasafed.tag=0.2.1 when installing KubeBlocks. For example:

helm install kubeblocks kubeblocks/kubeblocks --namespace kb-system --create-namespace \
  --version v1.0.0 \
  --set dataProtection.image.datasafed.tag=0.2.1

Please note that this is a workaround, and the official fix will have to wait for the next KubeBlocks release.

[StanleyWang-GitHub]

Hi @zjx20

Have tried, taking effect!

# kbcli backuprepo ls
NAME            STATUS   STORAGE-PROVIDER   ACCESS-METHOD   DEFAULT   BACKUPS   TOTAL-SIZE        
s3-backuprepo   Ready    s3-compatible      Tool            false     0         0 B