Feature Overview (aka. Goal Summary)  

OpenShift is traditionally a single-disk system, meaning the OpenShift installer is designed to install the OpenShift filesystem on one disk. However, new customer use cases have highlighted the need for the ability to configure additional disks during installation. Here are the specific use cases:

• Dedicated Disk for etcd:

• • As a user, I would like to install a cluster with a dedicated disk for etcd.
  • Our recommended practices for etcd suggest using a dedicated disk for optimal performance.
  • Managing disk mounting through MCO can be challenging and may introduce additional issues.
  • Cluster-API supports running etcd on a dedicated disk.
• Dedicated Disk for Swap Partitions:

• • As a user, I would like to install a cluster with swap enabled on each node and utilize a dedicated disk for swap partitions.
  • A dedicated disk for swap would help prevent swap activity from impacting node performance.
• Dedicated Disk for Container Runtime:

• • As a user, I would like to install a cluster and assign a separate disk for the container runtime.
• Dedicated Disk for Image Storage:

• • As a user, I would like to install a cluster with images stored on a dedicated disk, while keeping ephemeral storage on the node's main filesystem.

At a high level, this is how priorities look for each use case and platform:

ETCD

1. Azure
2. AWS
3. GCP
4. Others

SWAP

1. AWS
2. Bare Metal
3. GCP
   #Azure
4. Others

CONTAINER IMAGES

CONTAINER LOGS