-
Feature
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Product / Portfolio Work
-
-
False
-
-
False
-
S
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
Feature Overview (aka. Goal Summary)
Tow Node OpenShift with Arbiter (TNA) is currently supported and tested only with platform=baremetal. We need to support platform=none for certain types of installations, too.
Requirements (aka. Acceptance Criteria):
- Customers can install TNA with "platform=none" using all supported installation methods (UPI, Agent, Assistted etc) where it makes sense.
| 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
any other platform / cloud provider support keeps out of scope. TNA is targeting edge deployments only.
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
-
-
- Backlog
-
