Goal

Provide a way to install NodePools with varied architectures on the Agent platform.

Why is this Important?

This feature is important to enable workloads with different architectures (IBM Power/Z in this case) within the same Hosted Cluster.

Scenarios

• Cross-Architecture Use Case: A user has an x86 Hosted Cluster and wants to include at least one NodePool running with a ppc64le architecture.

• Multi-Architecture Workload Support: Scenarios where workloads demand compatibility with both x86 and alternative architectures like ARM64 or PowerPC.

Acceptance Criteria

Development (DEV):

• A valid enhancement is implemented if necessary, following community or internal guidelines.
• All upstream code and tests related to this feature are merged successfully.
• Upstream documentation is submitted and approved.

Continuous Integration (CI):

• All CI pipelines must run successfully with automated tests covering new functionality.
• Existing multi-architecture CI jobs are not broken by this enhancement.

Quality Engineering (QE):

• Polarion test plans are created and cover all necessary test cases.
• Automated tests are implemented and merged.
• Verification of documentation is completed during QE testing.

Dependencies (Internal and External)

• Management Cluster: Requires multi-architecture payload images for compatibility.
• Target Architecture: Architecture must already be included in the OCP payload for the feature to be functional.
• Multi-Cluster Engine (MCE): Must have builds compatible with the architecture used by worker nodes in the management cluster.