Feature Overview

Enable multi-tenant configurations for Tekton Results where the data for different tenants is stored in separate backend storages. 

Goals

Enable deployment of Tekton Results in multi-tenant clusters

Requirements

Use Cases

• Separate log storage backends per tenant in a multi-tenant cluster
• Separate pipelinerun metadata storage backends per tenant in a multi-tenant cluster

Out of scope

TBD

Dependencies

TBD

Background, and strategic fit

TBD

Assumptions

NA

Customer Considerations

NA

Documentation/QE Considerations

< What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)? >
< Does this feature have a doc impact? Possible values are: New Content, Updates to existing content, Release Note, or No Doc Impact?>
< Are there assumptions being made regarding prerequisites and dependencies?>
< Are there assumptions about hardware, software or people resources?>

Impact

TBD

Related Architecture/Technical Documents

<links>

Definition of Ready

• The objectives of the feature are clearly defined and aligned with the business strategy.
• All feature requirements have been clearly defined by Product Owners.
• The feature has been broken down into epics.
• The feature has been stack ranked.
• Definition of the business outcome is in the Outcome Jira (which must have a parent Jira).