A Technical Account Manager (TAM) for the Royal Bank of India (RBI) is working on a special project that intends to leverage Single Node OpenShift (SNO). They have reviewed existing documentation but require explicit confirmation on whether OpenShift Pipelines are officially supported on an SNO deployment.

Our assessment suggests that OpenShift Pipelines should be compatible with SNO as result of the upstream project efforts done in Tekton in this regard. However, before providing a definitive answer to the TAM, we need to double-check and confirm this internally and document it accordingly.

Goals

• Customer Enablement: Provides crucial information for a key customer (RBI) to proceed with their project planning.
• Customer Confidence: Builds trust and provides clear guidance to the TAM and RBI.
• Risk Mitigation: Ensures accurate information is provided, avoiding potential issues or rework later.
• A definitive "yes" or "no" answer regarding the support of OpenShift Pipelines on Single Node OpenShift (SNO).
• Any relevant documentation, prerequisites, or known limitations for running OpenShift Pipelines on SNO, if applicable.
•  

Requirements

• • (Optional) Use Cases

< What are we making, for who, and why/what problem are we solving?>

Out of scope

Non-OpenShift Single-Node clusters.

Dependencies

< Link or at least explain any known dependencies. >

Background, and strategic fit

< What does the person writing code, testing, documenting need to know? >

Assumptions

This is already supported in Tekton.

Customer Considerations

Nor further info is shared.

Documentation Considerations

< What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)? >

What does success look like?

< Does this feature have doc impact? Possible values are: New Content, Updates to existing content, Release Note, or No Doc Impact?>

QE Contact

< Are there assumptions being made regarding prerequisites and dependencies?>

< Are there assumptions about hardware, software or people resources?>

Impact

< If the feature is ordered with other work, state the impact of this feature on the other work>

Related Architecture/Technical Documents

<links>

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment