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

Introduce ClusterExtension creation form

XMLWordPrintable

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

      As a Cluster Administrator, I want a form-driven user interface for creating a ClusterExtension, So that I can configure my new ClusterExtension more easily and with fewer errors without manually writing YAML.

      Acceptance Criteria

      AC1: Navigate to Creation Form

      • Given the user is on the OpenShift Admin Console, a navigation path or button should direct the user to the "Create ClusterExtension" page.

      AC2: Default View and Switching

      • The "Create ClusterExtension" page must default to the "Form view".
      • A control (e.g., radio buttons) must allow the user to switch between "Form view" and "YAML view".

      AC3: Form Fields (Basic Configuration)

      • The form must include required input fields for:
        • ClusterExtension name.
          • Pre-filled from url search params
        • Package name.
          • Pre-filled from url search params
      • The form must include dropdown or selection fields for selecting or creating a new:
        • Namespace. (for operator controller, manifest, etc)
          • defaults to cluster extension name
          • suggests creation of dedicated operator namespace if one doesn't exist.
        • Service Account Name.
          • defaults to cluster extension name + "service-account"
          • must be in selected namespace
          • suggest creating dedicated service account for operator

      AC4: Package Resolution Constraints (optional form fields)

      • There must be a section which allows the user to refine the resolution criteria for the package
      • The advanced section must include fields for defining:
        • Version or Version range (e.g., 1.2.3 > 1.4.5). A text input field that allows users to input a specific version or version range.
          • Pre-filled from search params
        • Channel (e.g., via a dropdown or chip selection, such as Stable and Beta).
          • Pre-filled from search params
        • Catalog selector
          • Pre-filled from search params

      AC5: Form vs. YAML Disclosure

      • A prominent informational banner/disclosure must be present on the form view, warning the user that "Some fields may bot be represented in this form view. Please select 'YAML view' for full control of the ClusterExtension creation".

      AC6: Successful Creation

      • Clicking the "Submit" button must validate the form input and create the ClusterExtension resource.

      Technical Details

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

                Created:
                Updated: