Feature Overview
Support additional disk for control plane nodes in cloud providers (Azure, AWS and GCP) to be dedicated for ETCD
Goals
Allow the user to add additional dedicated disk for ETCD on OpenShift control plane nodes in Azure, AWS and Google Cloud while deploying OpenShift on this platforms in day-0
Requirements
- Support for configuring a secondary disk (for etcd) at installation
- Working CI environment for GA support
(Optional) Use Cases
- As an administrator, I would like to define a second disk for etcd on the control plane nodes at installation.
Out of Scope
Background, and strategic fit
Assumptions
Customer Considerations
Documentation Considerations
Questions to be addressed:
- What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)?
- Does this feature have doc impact? Yes, new install option.
- What concepts do customers need to understand to be successful in [action]? Following the documented minimum requirements and installation procedure.
- How do we expect customers will use the feature? For what purpose(s)? Adding a second disk for etcd at install time.
- What reference material might a customer want/need to complete [action]? None.
- Is there source material that can be used as reference for the Technical Writer in writing the content? Upstream docs.
- is duplicated by
-
OCPSTRAT-1592 Support for Configuring Additional Disks During OpenShift Installation - Phase I
- New
- is related to
-
OCPBUGS-32494 Not possible to create control plane machines with more than one blockDevice in AWS at IPI installation
- Closed
- relates to
-
SPLAT-1199 [azure] Evaluate isolated Data Disk to etcd
- Closed
-
OCPBUGS-32494 Not possible to create control plane machines with more than one blockDevice in AWS at IPI installation
- Closed