Description of problem: The disk size for Azure UPI[1] is not inline with IPI[2], likely resulting in not enough IOPS performance for etcd in UPI installations using the default values. Expected results: UPI and IPI must use the same defaults. Additional info: [1] https://github.com/openshift/installer/blob/2fa75fa52111009d2fd40d5a33b9cc01f037d501/upi/azure/05_masters.json#L259 [2] https://github.com/openshift/installer/blob/2fa75fa52111009d2fd40d5a33b9cc01f037d501/pkg/asset/machines/master.go#L249
Verified this bug with latest ARM templates, and works. After installation, check master OSDisk size, it is showing on Azure portal: Disk Configuration: 1024 GiB (Premium SSD)"
What is the migration plan for existing clusters? Is this something where folks will get an alert or other notification that etcd is suffering (or whatever) that points them to a doc chain that eventually says "you may want to try growing your control-plane disks with $PROCEDURE"?
This is UPI, the set of ARM templates we provide are just examples, a starting point for customers to write their own[1]. So I don't think this is the case for a migration plan, but I'm asking Abhinav to confirm. [1] https://docs.openshift.com/container-platform/4.4/installing/installing_azure/installing-azure-user-infra.html
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days