Pods not coming up when RHOCS Noobaa S3 storage used with image registry in RHOCP 4

Solution Verified - Updated -

Issue

  • The image-registry pod does not come up when RHOCS Noobaa S3 storage is used.
  • The cluster-image-registry-operator pod complains about the x509: certificate signed by unknown authority error.
# oc logs cluster-image-registry-operator-xxxxxxxxxx -n openshift-image-registry
2022-10-19T21:40:45.955166438Z caused by: Head "https://s3-openshift-storage.apps.example.com/obc-s3-c1720753-59f9-495d-84f4-4df5f1bf60e2": x509: certificate signed by unknown authority, requeuing

Environment

  • Red Hat OpenShift Container Platform 4
  • Red Hat OpenShift Container Storage 4

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