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

Enable and Disable Tech Preview Features via a Server Flag

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • OCP Console - Sprint 277

      As a Cluster Administrator, I want to control which Tech Preview features are active in the OpenShift console via a server-side configuration, so that I can selectively test new, unstable functionality in my clusters without exposing it to all users by default.

      Description

      To safely introduce new capabilities that are not yet ready for General Availability (GA), the console needs a mechanism to hide them behind a "feature flag." This flag will be disabled by default, ensuring a stable experience for all users. As an administrator, I need a way to opt-in to tech preview features on my development or staging clusters to evaluate them and provide early feedback. This should be managed through a central configuration on the console server, rather than individual user settings.

      Acceptance Criteria

      • A new configuration option is added to the console server as a command-line argument.
      • This configuration accepts a boolean value which enables or disables tech preview features.
      • By default, if the flag is not provided, tech preview features are disabled.
      • When the feature flag is enabled in the server configuration, all tech preview feature become visible and functional in the console UI.

       

      Note: Other option is to add additional ConsoleCapability enumerate to the console-operator config, which would either enable or disable the feature gate in the cluster.

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

                Created:
                Updated:
                Resolved: