-
Feature
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Product / Portfolio Work
-
-
100% To Do, 0% In Progress, 0% Done
-
False
-
-
False
-
S
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
Feature Overview (aka. Goal Summary)
Fully support adding worker nodes to Two Node OpenShift with Arbiter topology (2+1+n).
Goals (aka. expected user outcomes)
Customers with only two failure domains (rooms) at their edge locations want to be able to add worker nodes to a TNA cluster for scalability reasons.
This works technically already today, but needs to be fully supported / backed by a test case.
Requirements (aka. Acceptance Criteria):
- Customers can add worker nodes as day1 or day2 operation to a TNA cluster. If worker nodes are added, a minimum of two worker nodes is required (in line with the OCP bare metal minimum system requirement)
| Deployment considerations | List applicable specific needs (N/A = not applicable) |
| Self-managed, managed, or both | self-managed |
| Classic (standalone cluster) | yes |
| Hosted control planes | no |
| Multi node, Compact (three node), or Single node (SNO), or all | Multi node and Compact (three node) |
| Connected / Restricted Network | both |
| Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | x86_86 and ARM |
| Operator compatibility | full |
| Backport needed (list applicable versions) | no |
| UI need (e.g. OpenShift Console, dynamic plugin, OCM) | no |
| Other (please specify) | n/a |
Questions to Answer (Optional):
none
Out of Scope
none
Background
none
Customer Considerations
none
Documentation Considerations
- Support for adding worker nodes needs to be added to the TNA documentation. One sentence is enough.
Interoperability Considerations
none
- clones
-
-
- Release Pending
-
