How to solve the "x509: certificate signed by unknown authority" when the execution node pull the EE from the hub on aap-operator environment?

Solution Verified - Updated -

Issue

  • The job launching in an execution node can't pull the EE from the hub and throws:

    Error: initializing source docker://xxx-aap.apps.<ocpurl>.com/ee8:latest: pinging container registry xxx-aap.apps.<ocpurl>.com: Get "https://xxx-aap.apps<ocpurl>.com/v2/": tls: failed to verify certificate: x509: certificate signed by unknown authority

  • The aap url(hub) is an self-signed certificate and not published by the CA authority.

Environment

  • AAP2.5 operator

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