-
Epic
-
Resolution: Done
-
Blocker
-
None
-
Leveraging Log forwarder for Tekton Results
-
False
-
None
-
False
-
To Do
-
0% To Do, 0% In Progress, 100% Done
-
-
-
23
Epic Goal
- Using tkn client or kube API for storing logs is inefficient.
- We should store logs using a log forwarder like Vector or fluentd.
- In OpenShift, we have the OpenShift Logging operator and Loki.
We can map the logs in Lokistack to the runs using TektonResults.
Why is this important?
- ...
Scenarios
- ...
Acceptance Criteria (Mandatory)
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions::
- ...
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
- is cloned by
-
RHDEVDOCS-6195 DOC: Leveraging Log forwarder for Tekton Results
- Closed
- is documented by
-
RHDEVDOCS-6195 DOC: Leveraging Log forwarder for Tekton Results
- Closed