Epic Goal

• Enable users to deploy Windows CSI drivers, allowing the use of persistent storage for Windows workloads, and providing a migration path from in-tree storage.

Why is this important?

• Persistent storage is a necessary feature for production workloads on Kubernetes, and it is important that this functionality continue to work, even with the in-tree drivers being deprecated and removed from the kubelet.

Scenarios

1. As a developer using OpenShift, I want the Windows workloads I create to be able to read and write to storage which persists when pods are removed and re-created

Acceptance Criteria

• Windows nodes on OpenShift fulfill all the pre-requisites to run CSI node drivers
• DOC - Users have a clear understanding of how they can go about deploying CSI drivers on their cluster's Windows nodes.
• CI - Persistent storage is tested and working in end-to-end tests.

Dependencies (internal and external)

1. None

Open questions::

1. …

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>