Feature Overview (aka. Goal Summary)  

For environments that want to leverage multi-architecture compute functionality there is a need to provide an OCP cluster with an Arm based control plane and with x86 compute nodes. This would probably take the form of a compact Arm OCP cluster with x86 nodes added to it as a day 2 operation.

Goals (aka. expected user outcomes)

Testing and validation of adding x86 nodes to an Arm based compact cluster, users would be able to take this cluster, add the taint back in to stop workloads being scheduled on the control plane at the same time adding in x86 compute nodes to allow work to be scheduled on them.

Requirements (aka. Acceptance Criteria):

• Validate Arm compact cluster install
• Validate adding x86 nodes to said cluster
• Validate adding in a taint to stop jobs being scheduled on the Arm control plane

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.

Use Cases (Optional):

The major use case here is with the cloud providers who would like to use their Arm designed chips to run control plane infrastructure on - this leads to a cost efficient/power efficient experience for the provider and does not impact the customer/consumer as they do not need to change their applications to run on Arm

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

<your text here>

Out of Scope

This is orthogonal to Hosted Control Planes

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

<your text here>

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

<your text here>

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

<your text here>