Epic Goal

• Make it possible to deploy MicroShift without CSI snapshotting enabled.
• The CSI snapshot feature and CSI driver are orthogonal – neither should depend on the other. Both must be able to be added or removed independently.

Why is this important?

• The CSI snapshot controllers consume a bit of overhead. Users who are not using CSI storage likely do not want the snapshot controllers either.

Scenarios

1. A user deploys MicroShift with the CSI snapshot controllers and their own CSI driver.
2. A user deploys MicroShift with the CSI snapshot controllers and the LVMS driver.
3. A user deploys MicroShift without CSI or CSI snapshot.
4. A user deploys MicroShift with LVMS for CSI, but no snapshot controllers.
5. A user deploys MicroShift with CSI snapshot with all container images embedded in their OS image.

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. ...

Previous Work (Optional):

1. …

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>