Service Mesh Jaeger and Prometheus can't start in disconnected environment.

Solution Verified - Updated -

Issue

  • Unable to install Jaeger operator after creating a local Operator Lifecycle Manager and an ImageContentSourcePolicy.

  • Service Mesh instance of Prometheus fails with ImagePullBackOff error.

  • All the images are mirrored locally and they are referenced by digest in the ImageContentSourcePolicy. After installing the operator fails during creating an instance. It tries to pull registry.redhat.io/openshift4/ose-oauth-proxy:latest and registry.redhat.io/openshift4/ose-oauth-proxy:4.4.

  • Imagestream openshift/oauth-proxy shows x509 certificate signed by unknown authority error while accessing mirror registry.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Red Hat OpenShift Service Mesh (OSSM)
    • 2
  • Red Hat OpenShift Distributed Tracing (Jaeger)
  • Disconnected environment

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