Uploaded image for project: 'OpenShift SDN'
  1. OpenShift SDN
  2. SDN-1899

Support injecting of ca-bundle in PKCS#12 format and override it's name in CNO

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • SDN Core
    • Enhancements in CNO to support ca-bundle in PKCS#12 format and name override.
    • BU Product Work
    • False
    • False
    • To Do
    • OCPSTRAT-413 - Support injecting of ca-bundle in PKCS#12 format and override it's name in CNO
    • OCPSTRAT-413Support injecting of ca-bundle in PKCS#12 format and override it's name in CNO
    • 100% To Do, 0% In Progress, 0% Done
    • Undefined
    • 0
    • 0

      Goal

      • The goal in this epic to 
        • Allow users get the ca-bundle injected in their configmaps in PKCS#12 format using CNO.
        • Allow override the name of the ca-bundle.crt key in configmaps when injecting the CA bundle using the Cluster Network Operator.

      Why is this important?

      Both these features are requested by customers for following reasons.

      1. Customer deploying an EAP applications in their cluster which require trust in their corporate CA.  The only way to accomplish this is using initContainers to convert the .pem into .p12 or .jks for every single deployment or using 3rd party operators (which causes a poor image from OpenShift which could provide a full solution). Therefore we need a straightforward method to address this cumbersome process.  
      1. Not every single piece of software out there is configured to read the same filename `ca-bundle.crt` when reading certificates. Given that not everyone is capable of edit the deployments/deploymentconfigs when there's an operator controlling the resource and undoing the changes in the mounts. Therefore request to override the name of crt injected by the CNO operator.

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      Open questions::

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              Unassigned Unassigned
              ddharwar@redhat.com Deepthi Dharwar
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: