Uploaded image for project: 'OpenShift Console'
  1. OpenShift Console
  2. CONSOLE-4823

Allow users to switch between OLMv0 and OLMv1 catalog views

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • None
    • None
    • OCP Console - Sprint 280

      As a console user with the Tech Preview enabled, I want to see the new olmv1 catalog content by default in the Software Catalog, so that I can get accustomed to using the next-generation operators as my primary experience, while still having a simple way to switch back to the olmv0 catalog if needed.

      Acceptance Criteria

      • Given the OLMv1 Tech Preview feature is enabled for the cluster,
        When a user navigates to the OperatorHub page,
        Then the catalog view defaults to displaying operators from the olmv1 source.
      • Given the Tech Preview feature is enabled,
        Then a UI control (e.g., toggle or dropdown) is present for switching catalog sources.
        And this control clearly indicates that olmv0 is the alternative view.
      • Given the user is viewing the default olmv1 catalog,
        When they use the switcher to select the olmv0 view,
        Then the catalog list dynamically updates to show only operators from the olm.v0 source.
      • Given the user has switched to the olmv0 view,
        When they use the switcher to return to the olmv1 view,
        Then the catalog list dynamically updates to show the olmv1 operators again.
      • (Negative Case) Given the olmv1 Tech Preview feature is disabled for the cluster,
        Then the version switcher control is not visible, and the OperatorHub exclusively displays the standard olmv0 content.
      • Make the OLM switch persistent over logout and page refresh

      Technical Details

      • Feature Flag: The component must first check the console feature flag that governs this Tech Preview to determine its own visibility and default state.
      • API Integration: The frontend control must call the appropriate backend APIs that distinguish between olm.v0 and olm.v1 catalog sources.
      • UI Components: Use existing PatternFly components for the selector to ensure UI consistency with the rest of the console.
      • State Management: Consider using a URL query parameter (e.g., ?catalogSource=olmv1) to manage the view's state. This makes the specific catalog view linkable and easier to debug, even if session persistence isn't a firm requirement.

              rh-ee-jonjacks Jon Jackson
              rh-ee-jonjacks Jon Jackson
              None
              None
              YaDan Pei YaDan Pei
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: