What about using natively Tekton Dashboard for Jx3 #49
Description
Hello everyone,
After explaining it during the last Toc, i'm writting this enhancements:
In order to have less to maintain in the jx3 ecosystem, step by step,
what about firstly using natively the Tekton Dashboard instead of jx-ui ?
We did it and we are happy of this dashboard, here is a screenshot
Of course, we needed to configure lighthouse to automatically point to the tekton dashboard instead of the jx-one, don't worry it's possible.
When we changed our UI dashboard to the Tekton one, we obviously had to redo the Logs persistency part, back then following this old walkthrough, doing our own internal code for this => https://github.com/tektoncd/dashboard/blob/main/docs/walkthrough/walkthrough-logs.md
The great news is that tekton has finally implemented their own TEP-0117: Tekton Results Logs (tektoncd/community#994)
Tekton Results aims to help users logically group CI/CD workload history and separate out long term result storage away from the Pipeline controller.
Tekton Results is composed of 2 main components:
A queryable gRPC API server backed by persistent storage (see proto/v1alpha2 for the latest API spec).
A controller to watch and report TaskRun and PipelineRun updates to the API server.
Thanks to this PR => tektoncd/results#301 allowing to support log persistence outside of the host Kubernetes cluster. With this feature results will be able to store PipelineRun and TaskRun logs in the following persistent locations:
- File (PVC)
- S3 (S3 compatible storage)
In order to persist the Logs with this Tekton Result, these are the needed dependencies:
Kubernetes version: 1.22.x
Tekton Pipeline version: 0.42.0
We would need to plug differently lighthouse because through tekton dashboard we don't handle pipelineactivity that is specific of jx3
What do you think ? @msvticket @ankitm123 @tomhobson @babadofar @rajatgupta24