Add support for Elasticsearch/ELK as a backend option for Tekton Results

Goals

Current state today : the only supported backend for Tekton Results in Loki (via LokiStack). I.e. customers must install LokiStack and OpenShift Logging and configure forwarding of the logging information to LokiStack.

My customer already has an Elasticsearch stack that they use as a centralized logging for their systems and applications. And they wanted to forward their pipeline logs to this Elasticsearch stack. Knowing how popular Elasticsearch is, I won’t be surprised if this feature, if added, would be beneficial to our other customers.

So the goal of this RFE is to add Elasticsearch as a supported backend option for Tekton Results, and create necessary documentation on how to set it up.

Requirements

• • (Optional) Use Cases

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

Out of scope

<Defines what is not included in this story>

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

Customer has an existing OpenShift cluster v.4.16+ with Tekton Pipelines Operator v 1.18.1+. And the customer also has an existing Elasticsearch system that they use to centralize log collection/analysis for all systems and applications in their environment.

Customer Considerations

< Are there specific customer environments that need to be considered (such as working with existing h/w and software)?>

Documentation Considerations

We would need documentation to set up this feature on OpenShift and Tekton Results.

What does success look like?

Elasticsearch is a supported backend option for Tekton Results, and we have necessary documentation on how to set it up.

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