XMLWordPrintable

Details

    • Feature
    • Resolution: Done
    • High
    • None
    • None
    • Operator
    • None
    • 3
    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% 0%
    • 0
    • 0.0

    Description

      Description:

      This feature introduces a user-controlled feature gating mechanism to our OpenShift Operator. The mechanism will not only enable controlled deployment of new features but also allow users to enable certain features on demand via a configuration mechanism (like a ConfigMap). The product team will decide which features are enabled by default and which are supported when manually enabled by users.

      Objectives:

      1. User-Controlled Feature Enablement: Users can enable certain non-default features through a configuration interface such as a ConfigMap. This empowers users to opt-in for features that are relevant to their specific use cases.
      2. Default and Supported Features: The product team retains control over the default state of new features, ensuring that only fully tested and stable features are enabled by default. The team also determines the level of support for features that users can enable manually.
      3. Enhanced Testing and Feedback: Supports testing new features in realistic settings and gathering user feedback for improvements.
      4. Stability and Reliability: Ensures system stability is maintained as new features are introduced and tested.
      5. Flexible Feature Management: Enables quick adjustments to feature states without system downtime or full redeployments.

      Acceptance Criteria:

      1. Integration of the feature gating mechanism with the current OpenShift sandboxed containers operator.
      2. Users can enable/disable select features through a ConfigMap or similar configuration tool.
      3. Default feature states are set, and supported features for user enablement are clearly documented.
      4. Features can be toggled without affecting system stability or requiring full redeployment.
      5. Successful demonstration of both default and user-enabled features in a controlled environment.

      Dependencies:

      •  

      Notes:

      • The feature list available for user enablement should be thoroughly reviewed and approved by the product team.

      Open questions:

      • What problems can occur when introducing the feature gating?
      • What needs to be done for the transition?

      Attachments

        Activity

          People

            beraldoleal Beraldo Leal
            jfreiman Jens Freimann
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: