XMLWordPrintable

    • BU Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-1131MicroShift Enhancements 2024 for Industrial, Retail and Public Sector edge customers
    • 100% To Do, 0% In Progress, 0% Done
    • S
    • 0

      Feature Overview (aka. Goal Summary)  

      Provide support for cert-manager running on MicroShift 

      Goals (aka. expected user outcomes)

      MicroShift customer can use cert-manager on MicroShift to create certificates used by their components. 

      Requirements (aka. Acceptance Criteria):

      1. cert-manager can be installed using OLM on MicroShift. 
      2. Optional: cert-manager can be installed using an rpm package (microshift-cert-manager)
      3. The core cert-manager functionality must be available
        1. Support for integrating with external certificate authorities (incl. same list of issuer types)
        2. Tools to manage certificates (incl. dynamic creation)
        3. Automatic certificate renewal
      4. MicroShift supports only the core k8s API. That means that all dependencies in cert-manager on OpenShift specific APIs need to be turned into weak references. This means to probe for the API to exist and gracefully handle if not present. The functionality associated with those APIs is not available on MicroShift. APIs known to be used by cert-manager and not available on MicroShift:
        1. *.config.openshift.io
        2. gateway.networking.k8s.io 

      Questions to Answer (Optional):

      Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

      tbd

      Out of Scope

      High-level list of items that are out of scope.  Initial completion during Refinement status.

      tbd

      Background

      Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

      <your text here>

      Customer Considerations

      Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

      <your text here>

      Documentation Considerations

      Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

      <your text here>

      Interoperability Considerations

      Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

      <your text here>

            rh-ee-npng Nick Png
            dfroehli42rh Daniel Fröhlich
            Shauna Diaz Shauna Diaz
            Evgeny Slutsky Evgeny Slutsky
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated: