-
Feature
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
BU Product Work
-
False
-
-
False
-
-
100% To Do, 0% In Progress, 0% Done
-
0
Feature Overview (aka. Goal Summary)
This feature is to bring parity for other architectures (IBM Power and IBM Z) for the CSI Secrets Store operator
Goals (aka. expected user outcomes)
The CSI Secrets Store Operator will be available for and work on IBM Power and IBM Z Systems
Requirements (aka. Acceptance Criteria):
- Secrets Store built for IBM Power
- Secrets Store built for IBM Z
- Test plan for both architectures
- Documentation updated for new arch support
Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed. Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.
| Deployment considerations | List applicable specific needs (N/A = not applicable) |
| Self-managed, managed, or both | Y |
| Classic (standalone cluster) | Y |
| Hosted control planes | Y |
| Multi node, Compact (three node), or Single node (SNO), or all | Y |
| Connected / Restricted Network | Y |
| Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | IBM Power, IBM Z |
| Operator compatibility | n/a |
| Backport needed (list applicable versions) | n/a |
| UI need (e.g. OpenShift Console, dynamic plugin, OCM) | n/a |
| Other (please specify) |
Use Cases (Optional):
Questions to Answer (Optional):
Out of Scope
Background
Customer Considerations
Documentation Considerations
An update to the CSI Secrets Operator documentation - will need to co-ordinate with the team that owns the operator
Interoperability Considerations
