Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-797

Enhance MicroShift Community experience

XMLWordPrintable

    • Proactive Architecture
    • False
    • Hide

      None

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

      Feature Overview (aka. Goal Summary)  

      MicroShift currently has no decent community experience. Access to MicroShift's components are locked behind authentication walls. The goal of this feature is to re-vamp microshift.io to provide a positive experience for community members. E.g. use / integrated with OKD to make upstream use of MicroShift quick and easy. 

      Goals (aka. expected user outcomes)

      Be able to test-drive MicroShift with pure community bits, no sub, no pull secreted needed.

      This relies on making CNI+CSI driver configurable/pluggable to point to e.g. OKD or other community implementations (e.g. flannel for CNI, or NFS for CSI).

      Update / enhance the microshift.io website with current documentation and guidance on how to contribute.

      Requirements (aka. Acceptance Criteria):

      • As community user, I can easily install MicroShift to my Centos Stream system, without the need of a subscription or pull secrets.
      • As community developer, I can install MicroShift by executing a one line shell command on my existing fedora based linux distro.
      • As community developer, I can easily contribute to MicroShift by submitting pull requests.

      Questions to Answer (Optional):

      How can we leverage materials / processes from OKD?

      Out of Scope

      Supporting other CSI drivers then the ones decided for MicroShift currently. While community might plug in other providers, it has to be made clear that Red Hat does not provide any support, if other providers are being used.

      Current work on integrating Flannel as an alternative to OVK should satisfy the community's networking needs.

      Background

      Community experience on microshift.io was neglected in the past in favor of getting to GA with MicroShift.

      Customer Considerations

      Customers evaluate RH against capacity to maintain an upstream variant of enterprise features, thus the lack of an upstream may hinder sales.

      Customers may use upstream variants as trial runs of RH offerings.

      Documentation Considerations

      No change to enterpise docs, everything needs to be upstream docs. The assumption is that existing docs on github.com/openshift/microshift can be easily used as community docs.

      Interoperability Considerations

      Work with OKD team what can be re-used from them.

      Explore integration upstream MicroShift into OKD's build, test, and publishing pipelines.

       

            dfroehli42rh Daniel Fröhlich
            dfroehli42rh Daniel Fröhlich
            Jeremy Peterson Jeremy Peterson
            Jon Cope Jon Cope
            Daniel Fröhlich Daniel Fröhlich
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: