Feature Overview (aka. Goal Summary)  

Enable OpenShift clusters deployed on AWS public cloud to run compute nodes on AWS Outposts.

This is a follow-up work on AWS Outposts (remote worker node) support, that was introduced in OCPSTRAT-470.

Goals (aka. expected user outcomes)

As a user, I want to deploy OpenShift on AWS public regions with compute Nodes running on my local AWS Outposts so I can run specific workloads on this "edge" location.

As a user, I want to extend my existing OpenShift cluster running on AWS public regions adding new compute Nodes on my local AWS Outposts so I can run specific workloads on this "edge" location.

Requirements (aka. Acceptance Criteria):

The user will be able to deploy OpenShift on day-0 on AWS public regions with compute Nodes running in the local Outposts into an existing VPC.

The user will be able to extend an existing OpenShift cluster running on AWS public regions on day-2, adding compute Nodes to run in the local Outposts into an existing VPC.

Use Cases (Optional):

All the details have been defined in the feature enhancement and this work is based in the previous work to enable this feature as TP.

Out of Scope

Enable OpenShift to deploy control plane Nodes on AWS Outposts.

Create the required VPCs and network configuration to link the Outposts environment with AWS public cloud region

Background

The background for this feature is all captured in the previous work in OCPPLAN-9617 and OCPSTRAT-470.

Documentation Considerations

Additional documentation will be required to cover any changes coming from this Feature that was not documented already while enabling Outposts as TP. AWS Outposts is offered in different "flavours"; documentation must include which of these "flavours" we test/support for OpenShift