-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Velero Kopia Integration - Don't support Self-signed Certificate for S3 Compatible Storage #5123
Comments
Thanks @Lyndon-Li |
Couldnt this be solved by mounting the certificate into the ca store on the container via a secret? |
@vrabbi The problem is there is no way to tell Kopia to search a certificate outside of the system's CA store. On the other hand, there is not an easy way to make a certificate into the system's CA store without changing the docker image. |
Remove from v1.10 due to limitation. |
I have a PR'd an attempt to solve this issue: kopia/kopia#2845 |
@babs Thanks for letting us know, we will track the issue and PR. |
Let's bump up Kopia to fix this issue in v1.12 timeframe. |
@reasonerjt Kopia 0.13 including the fix is in RC phase, couldn't it be integrated in 1.11 if kopia goes stable before ? |
@babs |
Fixed by #6268 |
Good news, thanks! |
Some S3 compatible storage provides secure connection with self-signed certificate.
The Restic path supports this already since restic accepts a flag in all its related CLIs, so that the caller could provides a certificate file.
However, the Kopia path doesn't support this at present, because the backend Kopia repository doesn't accept a certificate file. There is a Kopia issue kopia/kopia#1443.
We will mark this as a limitation in Velero for now. When Kopia fix the above issue, we will be able to fix this limitation with minor code change to Velero.
The text was updated successfully, but these errors were encountered: