This Epic is to track the GA of this feature

Goal

• Make available the Google Cloud File Service via a CSI driver, it is desirable that this implementation has dynamic provisioning
• We are currently limited to block / RWO only (4.8 GA)

Why is this important?

• There is a know storage gap with google cloud where only block is supported
• More customers deploying on GCE and asking for file / RWX storage.

Scenarios

1. Install the CSI driver
2. Remove the CSI Driver
3. Dynamically provision a CSI Google File PV*
4. Utilise a Google File PV

• If dynamic provisioning is not possible this could be looked at

  Acceptance Criteria

• CI - MUST be running successfully with tests automated
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Customers::

• Telefonica Spain
• Deutsche Bank

Done Checklist

• CI - CI is running, tests are automated and merged.
• 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>