1. Proposed title of this feature request

When installing an OpenShift cluster on Azure, two storage accounts are created using LRS (Locally redundant storage) redundancy. It could be useful to allow modifying this behaviour via install-config.yaml file customisation.

2. What is the nature and description of the request?

When an OpenShift cluster is installed on Azure, the storage accounts (for registry and CoreOS vhd) are created using LRS (Locally redundant storage) redundancy instead of ZRS (Zone-redundant storage) redundancy.

It could be useful to have a customisation in the install-config.yaml file to change this. For example, add a customisation like platform.azure.storageAccountRedundancy that allows setting the storage account redundancy.

3. Why does the customer need this? (List the business requirements here)

When the OpenShift cluster is installed, the storage accounts are created using LRS redundancy. So, if the availability zone that contains the storage account goes down, the registry and the CoreOS image are not going to be available, causing issues when using the internal registry and scaling nodes.

It could be useful to allow modifying this, to avoid problems if the availability zone that contains the internal registry and the internal CoreOS image goes down.

Some customers may prefer having the storage accounts using ZRS instead of LRS to avoid availability issues.

At the moment, it is possible changing the storage account redundancy using Azure support or the User-initiated conversion. But it could be useful to allow the modification on installation time, to avoid changing it as a day-two operation.

4. List any affected packages or components.

OpenShift installer

Image registry

CoreOS disk image vhd