Comments (19)
@AlanGreene it's been awhile since we've touched base on this. Any updates on the dashboard side for how to get started experimenting?
from results.
/lifecycle frozen
This is something we still want to get to, but need help from the dashboard team
from results.
alternatively/additionally, provide better integration into the existing UI, so for example we might populate the existing PipelineRun details page with data from the Results API if the resources are no longer available on the cluster
+1 to the second approach recommended by @AlanGreene - It would be great to leverage results api to make the PipelineRun
link (e.g. namespaces/tekton-pipelines/pipelineruns/foo-123
permanent with minimal overhead in etcd as well as persist the logs as mentioned in: #198
These features would greatly improve the out of the box experience of Tekton IMO.
from results.
- alternatively/additionally, provide better integration into the existing UI, so for example we might populate the existing PipelineRun details page with data from the Results API if the resources are no longer available on the cluster
This seems like the ideal route to me. Results providing the historical record / source of truth for anything that's reached a Completed ( / deleted) state.
@wlynch do you think that's fair assessment?
Yup! The Result API also captures data for unique instances of Runs with the same name (e.g. if you create->delete->create) which would probably also be useful for the dashboard.
Modeling the dashboard on the Result API would also let us display related data (e.g. PipelineRun + TaskRuns) in groups.
@AlanGreene I added a discussion item for the March 8th Dashboard WG so we can talk about questions/ideas!
from results.
Unfortunately not an idea of how to go forward but want to say that this is really exciting. Due to relying on the Kubernetes APIs the dashboard really struggles when there are lots of resources. Implementing proper pagination is difficult and also filtering possibilities are limited. As a workaround, we try to keep the number of resources low (e.g. using https://github.com/tektoncd/experimental/tree/master/pipeline/cleanup#cleanup-old-taskruns-and-pipelineruns) but ideally we should be able to keep as much history for e.g. all executions of a pipeline as we want and not as technically limited ;)
Would be awesome if results is the solution!
from results.
@Fabian-K Sorry I missed this! But yes, that's the goal for this project. :)
This issue is scoped purely for integrating with the Tekton Dashboard, but you'll probably find #59 useful to your use case!
from results.
https://github.com/tektoncd/dashboard/blob/master/docs/extensions.md looks like a promising way to hook into the Dashboard.
from results.
@wlynch I'd love to talk more about the desired user experience for viewing / interacting with the Results data. There are plenty of options to explore depending on the desired outcome.
At a high level I see 2 main options for the user:
- add new pages to the Dashboard to surface data from the Results API using the existing extensions mechanism
- Note: Dashboard extensions were originally intended to allow for both adding new pages and customisation of existing pages. Unfortunately this plan was never fully realised and extensions have remained pretty basic, only supporting the addition of new pages to the app (either simple auto-generated pages for Kubernetes resources, or custom UI similar to the deprecated webhooks-extension).
- alternatively/additionally, provide better integration into the existing UI, so for example we might populate the existing PipelineRun details page with data from the Results API if the resources are no longer available on the cluster
There are some planned changes to the Dashboard's API / data layer that may make integration / customisation easier in future, and some other challenges such as auth that we'll need to address too.
from results.
- alternatively/additionally, provide better integration into the existing UI, so for example we might populate the existing PipelineRun details page with data from the Results API if the resources are no longer available on the cluster
This seems like the ideal route to me. Results providing the historical record / source of truth for anything that's reached a Completed ( / deleted) state.
@wlynch do you think that's fair assessment?
Are the dashboard's data layer plans related to the redux removal issue or documented elsewhere?
from results.
Are the dashboard's data layer plans related to the redux removal issue or documented elsewhere?
Yes that's the first part of it, a major simplification of the data layer (and corresponding reduction in boilerplate) so we can more easily plugin additional / alternative sources while solving some of the performance and caching issues we have today. I need to flesh out the plan a bit more and document it so we can start to make progress. I have my hands full for the next 1 - 2 weeks but will try to get something on paper asap for others to review.
from results.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen
with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
from results.
Is this issue still actively being worked on?
(I came here from the Dashboard project due to the slowness of the dashboard)
from results.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen
with a justification.
/lifecycle rotten
Send feedback to tektoncd/plumbing.
from results.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
with a justification.
Mark the issue as fresh with /remove-lifecycle rotten
with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen
with a justification.
/close
Send feedback to tektoncd/plumbing.
from results.
@tekton-robot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen
with a justification.
Mark the issue as fresh with/remove-lifecycle rotten
with a justification.
If this issue should be exempted, mark the issue as frozen with/lifecycle frozen
with a justification./close
Send feedback to tektoncd/plumbing.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
from results.
@pietervincken: You can't reopen an issue/PR unless you authored it or you are a collaborator.
In response to this:
/reopen
This feature is still missing. IIRC this was the endgoal of this subproject?
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
from results.
Can we re-open this issue? We're running Tekton on a larger scale (2k+ pipelineruns, 20k+ taskruns active in the cluster) so we'd be very interested in having the ability to not rely on the Kubernetes API for looking into results of a pipeline. Currently we need to very aggressively clean the runs in order for the dashboard to stay performant.
from results.
Hi, guys, any progress on the integration?
Currently it's not possible to view the build status of a project via dashboard like jenkins, and it's also not directly supported through the pipeline metrics(use grafana + prometheus). So I'm wondering if this could be achived by tekton results?
from results.
/area roadmap
from results.
Related Issues (20)
- Upgrade knative/pkg to latest 1.8 or 1.9 commits HOT 2
- Document how to add another config overlay HOT 3
- Provide Database Migration Scripts for #334 HOT 11
- better shield DB/S3 credentials provide to results API deployment HOT 6
- New release v0.6.0 HOT 7
- Make e2e tests more configurable HOT 2
- Record Kubernetes Events related to PipelineRuns/TaskRuns
- Add Rekor Attestations/Chains for Results Release HOT 8
- E2E tests use functions not yet available in go 1.18 HOT 1
- CEL Filters across Results return multiple duplicate records HOT 7
- Bundling the TKN Results with TKN CLI HOT 4
- [CLI] Add support for self signed certificate/insecure tls HOT 3
- Global Retention Policies HOT 6
- [CLI] Global flag not working from commandline HOT 3
- Passing Storage(S3, AWS) keys via kubernetes secrets HOT 3
- [Docs]: Integrate tkn-results docs with main docs HOT 1
- Include `tkn-results` in our tests HOT 3
- Auth failure for admin and edit roles users HOT 1
- improve api server auth messages HOT 1
- CEL filter with NOT operator with a group crashes the API server HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from results.