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

[DNM] enable immediate pruning of PipelineRuns in Tekton Results #868

Conversation

ramessesii2
Copy link
Member

No description provided.

Signed-off-by: Satyam Bhardwaj <sabhardw@redhat.com>
@ramessesii2 ramessesii2 changed the title enable immediate pruning of PipelineRuns in Tekton Results [DNM] enable immediate pruning of PipelineRuns in Tekton Results Nov 27, 2023
@Roming22
Copy link
Contributor

As discussed, we'll wait for tektoncd/results#672 to be merged and deployed, and deactivate the default pruner before merging this PR.

@@ -19,7 +19,7 @@ spec:
"-auth_mode",
"token",
"-completed_run_grace_period",
"10m",
"-1", # anything less than 0 means completed PipelineRuns will be pruned immediately.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This might have undesirable consequences because the streaming of logs happens in a separate go routine which doesn't negotiate with the controller workflow and hence the deletion.

https://github.com/tektoncd/results/blob/097030b9f52bf01149f7555d86b26f7a77327c60/pkg/watcher/reconciler/dynamic/dynamic.go#L323-L339

There is an open bug on this.
tektoncd/results#514

But it can be tested in staging. My guess there'll be a race condition.

@ramessesii2
Copy link
Member Author

Closed in favor of #905

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

Successfully merging this pull request may close these issues.

None yet

3 participants