Uploaded image for project: 'Red Hat OpenShift AI Engineering'
  1. Red Hat OpenShift AI Engineering
  2. RHOAIENG-7050

Implement feature flags for operator

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Platform
    • Implement feature flags for operator
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do
    • No
    • Testable

      Problem Statement:

      There are feature parities between ODH and RHOAI. For example, a component is incubating in ODH for multiple releases before going into RHOAI. Such cases prevents operator from having 1-1 sync between commits in upstream and downstream. Implement Feature Flags for the operator to exclude incubating features. In the meantime, we just exclude these commits from cherry-pick.

       

      Advantages of Introducing Feature Flags

      1. Improved sync between ODH and RHOAI
      2. For ODH customers/users easier adoption to OpenShift AI
      3. For OpenShift AI customers, way to test out upcoming features.

       

      Considerations

      1. ODH component integrations consists of quay images. Would it be okay to include such features behind a feature flag in OpenShiftAI
      2. Effectively handling CRD updates.

       

      Implementation

      1. We should be able to add optional fields in CRDs to enable feature flags.

       

       

            ahmedabdalla Ahmed Abdalla
            vhire Vaishnavi Hire
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: