You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: