Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-2343

Add warning while enabling techPreviewNoUpgrade feature

XMLWordPrintable

    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Feature Overview (aka. Goal Summary)  

      Add a clear, non-bypassable warning when enabling TechPreviewNoUpgrade feature set to inform users about the lack of rollback support and production readiness.

      Goals (aka. expected user outcomes)

      Users will be explicitly warned about the implications of enabling TechPreview features, preventing accidental production use and subsequent requests for unsupported rollback operations

      Requirements (aka. Acceptance Criteria):

      • A clear, non-bypassable warning message must be displayed when TechPreviewNoUpgrade or any TechPreview feature gate is selected during Day-1 cluster installation (e.g., via openshift-install or assisted installer).
      • A clear, non-bypassable warning message must be displayed when updating the FeatureGate resource in a running cluster on Day-2.
      • The warning message should state: "⚠️ You are enabling TechPreview features. These are not supported for production use. Once enabled, they cannot be rolled back or selectively removed. The only recovery path is to destroy and recreate the cluster. Proceed only if this is acceptable."
      • The system should prevent users from proceeding without acknowledging the warning.

      Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

      Deployment considerations List applicable specific needs (N/A = not applicable)
      Self-managed, managed, or both  
      Classic (standalone cluster)  
      Hosted control planes  
      Multi node, Compact (three node), or Single node (SNO), or all  
      Connected / Restricted Network  
      Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x)  
      Operator compatibility  
      Backport needed (list applicable versions)  
      UI need (e.g. OpenShift Console, dynamic plugin, OCM)  
      Other (please specify)  

      Customer Considerations

      Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

      <your text here>

      Documentation Considerations

      Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

      <your text here>

      Interoperability Considerations

      Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

      <your text here>

              linnguye.openshift Linh Nguyen
              linnguye.openshift Linh Nguyen
              None
              None
              None
              Yunfei Jiang Yunfei Jiang
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: