Unable to resolve parent devworkspace when using self-signed certificates on disconnected cluster

Solution Verified - Updated -

Issue

  • When using self-signed certificates to host a devworkspace on an air-gapped cluster, attempting to start a devworkspace that refers to a parent devworkspace via a URI results in failure. The parent devworkspace remains unresolved, and the devworkspace displays the following error:

    x509: certificate signed by unknown authority error
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.z
  • Red Hat OpenShift DevSpaces
    • 3.12+

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