Uploaded image for project: 'OpenShift Image Registry'
  1. OpenShift Image Registry
  2. IR-390

Expose registry CAs as one to MCO

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • openshift-4.14
    • None
    • None
    • None
    • Sprint 238

      To enable the MCO to replace the node-ca, the registry operator needs to provide its own CAs in isolation.

      Currently, the registry provides its own CAs via the "image-registry-certificates" configmap. This configmap is a merge of the service ca, storage ca, and additionalTrustedCA (from images.config.openshift.io/cluster).

      Because the MCO already has access to additionalTrustedCA, the new secret does not need to contain it.

       

      ACCEPTANCE CRITERIA

      TBD

              fmissi Flavian Missi
              fmissi Flavian Missi
              XiuJuan Wang XiuJuan Wang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: