Feature Overview (aka. Goal Summary)  

Google introduced support for a new disk type "hyperdisk-balanced-high-availability" we need to support it in OCP.

Hyperdisk Balanced High Availability volumes to synchronously replicate data across two zones in the same region. You can also use Hyperdisk Balanced High Availability volumes in scenarios that require write access to the same volume multiple zones.

https://docs.cloud.google.com/compute/docs/disks/hd-types/hyperdisk-balanced-ha

Goals (aka. expected user outcomes)

Support hyperdisk-balanced-high-availability disk type

We're not introducing it as default nor automatically create a SC, admin would need to create a new SC

Requirements (aka. Acceptance Criteria):

Enable support in the driver + CI

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.

Use Cases (Optional):

1. As an admin I want to offer hyperdisk-balanced-high-availability to my users through a new SC
2. As a user I want to deploy applications backed by hyperdisk-balanced-high-availability in order to get data redundancy.

Questions to Answer (Optional):

STOR-2792 

Out of Scope

Limited to manual creation of the SC by the admin, no automation by GCP PD CSI operator

Background

hyperdisk-balanced-high-availability is important for customers who want data replication; also we need to be in sync with what GCP offers to the marker.

Customer Considerations

hyperdisk is only supported on C3/N4

Documentation Considerations

Add hyperdisk-balanced-high-availability support in the hyperdisk doc section + relnotes

Interoperability Considerations

GCP only