Volsync operator doesn't work with self-signed certificates

Solution Verified - Updated -

Issue

  • Volsync operator pod fails when self-signed certificates have been used.
Starting container
VolSync restic container version: ACM-0.5.1-eac9acc
backup
Testing mandatory env variables
== Checking directory for content ===
== Initialize Dir =======
Fatal: create repository at s3:<bucket -url>/openshift-adp/snapcontent-9371765c-3e8f-4529-bd74-ab078b420587-pvc failed: client.BucketExists: Head <bucket -url>"/": x509: certificate signed by unknown authority

Environment

  • Red Hat OpenShift Platform(RHOCP)
    • 4.x
  • OADP v1.1.1
  • volsync v0.5.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content