Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-6255

Include CA in the Ingress Controller certificate when cert is created by Cert Manager

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • cert-manager
    • None
    • False
    • None
    • False
    • Not Selected

      1. Proposed title of this feature request

      Cert Manager creates a secret containing tls.crt, tls.key and ca.crt. Then the Ingress operator creates the secret for the Ingress.
      However, the CA is not included in the secret, the operator only creates the secret for Ingress Conrtoller from tls.crt and tls.key, omitting the CA.

      2. What is the nature and description of the request?

      When the certificate is created for the Ingress by cert manager - the CA is excluded from the tls.crt and saved as "ca.crt" in the secret.
      Ability for the router to automatically attach the CA certificate in the server requests to the clients.

      3. Why does the customer need this? (List the business requirements here)

      The CA from the cert manager then needs to be included in the client application. If the certificate is intermediate and client trusts only Root CA - then the client is not able to verify the trust.

      4. List any affected packages or components.

      ingress controller
      router
      cert-manager

              rh-ee-npng Nick Png
              rhn-support-vwalek Vladislav Walek
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: