Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resource Cleanup / Long-Term Storage #1646

Closed
Fabian-K opened this issue Nov 29, 2019 · 1 comment
Closed

Resource Cleanup / Long-Term Storage #1646

Fabian-K opened this issue Nov 29, 2019 · 1 comment

Comments

@Fabian-K
Copy link
Contributor

Hi,

when a pipeline is executed, tekton currently retains the Pod used for the execution. Over time, this results in quite some Pods in the Completed phase - which might cause issues on other parts (e.g. grafana/loki#1315). Is there a reason to keep the pods around or can they be safely deleted (thinking about logs, metrics, status information ...)?

Also regarding e.g. PipelineRuns or TaskRuns - the information that the pipeline was executed is for sure worth keeping. However, does this cause issues on the API Server once 1.000+, 10.000+ or even more entries are reached?

Thanks,
Fabian

@imjasonh
Copy link
Member

imjasonh commented Dec 2, 2019

This seems like a duplicate of #454

Basically, we do have vague plans to persist execution history to some datastore outside of the cluster's etcd. This would also let us clean up the completed Pods etc.

Right now we only have a design proposal that summarizes to "persist execution history to some datastore outside of the cluster's etcd" 😄but I plan to prototype some things and add more detail to this soon.

@imjasonh imjasonh closed this as completed Dec 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants