Uploaded image for project: 'OpenShift Storage'
  1. OpenShift Storage
  2. STOR-1344

Upstream GA Tracking: Non-graceful node shutdown

XMLWordPrintable

    • Upstream GA Tracking: Non-graceful node shutdown
    • Upstream
    • 0
    • False
    • None
    • False
    • Green
    • To Do
    • OCPSTRAT-724 - Non-graceful node shutdown
    • OCPSTRAT-724Non-graceful node shutdown
    • 0% To Do, 0% In Progress, 100% Done

      Epic Goal

      Support upstream feature "Non-graceful node shutdown" in OCP as GA, i.e. test it and have docs for it. It is currently supported as technology preview in 4.13, see STOR-744

      Why is this important?

      • We get this upstream feature through Kubernetes rebase. We should ensure it works well in OCP and we have docs for it.

      Upstream links

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. External: the feature is currently scheduled for GA in Kubernetes 1.28, i.e. OCP 4.15, but it may change before Kubernetes 1.28 GA.

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              rhn-engineering-jsafrane Jan Safranek
              rhn-engineering-jsafrane Jan Safranek
              Rahul Deore Rahul Deore
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: