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
Is your feature request related to a problem? Please describe.
We have received a few queries from customers where they have configured s3 S3-compatible location with custom certificate.
They wanted to use BackupDataAll and RestoreDataAll function in the Blueprint. But it fails with x509: certificate signed by unknown authority.
We should add a way to disable TLS and pass custom certs to the functions so that it can be used internally for the authentication.
Describe the solution you'd like
Maybe we can add an additional function arg to disable TLS.
For passing custom certificates, we can create a secret/configmap and pass the resource name as an argument
The text was updated successfully, but these errors were encountered:
Thanks for opening this issue 👍. The team will review it shortly.
If this is a bug report, make sure to include clear instructions how on to reproduce the problem with minimal reproducible examples, where possible. If this is a security report, please review our security policy as outlined in SECURITY.md.
If you haven't already, please take a moment to review our project's Code of Conduct document.
Is your feature request related to a problem? Please describe.
We have received a few queries from customers where they have configured s3 S3-compatible location with custom certificate.
They wanted to use BackupDataAll and RestoreDataAll function in the Blueprint. But it fails with
x509: certificate signed by unknown authority
.We should add a way to disable TLS and pass custom certs to the functions so that it can be used internally for the authentication.
Describe the solution you'd like
Maybe we can add an additional function arg to disable TLS.
For passing custom certificates, we can create a secret/configmap and pass the resource name as an argument
The text was updated successfully, but these errors were encountered: