Spawned from a discussion in https://bugzilla.redhat.com/show_bug.cgi?id=1703581 . Users should know how to create a separate PIOPS volume specifically for etcd. This will likely start as documentation, and possibly move to install-time configuration if it is useful enough.
This is currently possible (changing the root volume for the master): https://github.com/openshift/installer/blob/master/docs/user/aws/customization.md Also, via Hive: https://github.com/openshift/hive/blob/master/pkg/apis/hive/v1alpha1/machinepools.go#L59-L66
Deferring "separate" volume question to 4.2.0 and the CORS stories we have for it. For the 4.1.0 release, adjusting the main master volume to the right size/type should get us what we need.
At what point will 4.1 and 4.2 clusters that grow in size be subject to hitting scale issues because of this? Do we need to have a separate bug, epic, jira for tracking how to mitigate this and move etcd to more performant storage post-install?
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days