Tekton Pruner Is Not Deployed
Problem Description
The Tekton Pruner components are missing after installation, so pruning does not work.
Error Manifestation
- The
tekton-pruner-controllerandtekton-pruner-webhookDeployments are not present in thetekton-pipelinesnamespace. - The corresponding Pods are not created.
Root Cause Analysis
Tekton Pruner is an event-based pruner and is disabled by default.
If the job-based pruner is not disabled, or the event-based pruner remains disabled, the operator will not deploy the Tekton Pruner components.
For more information, see Tekton Pruner Configuration.
Troubleshooting
The following instructions assume that you have installed Tekton into the tekton-pipelines namespace by default.
If you have installed it into a different namespace, please replace tekton-pipelines with your namespace.
Enabling the Pruner deletes runs at once, in every namespace it covers. Before you enable it, read the warning in Recommended Settings of Namespace Configuration and follow the steps there.
Follow these steps to enable the event-based pruner. They need permission to edit the cluster-scoped TektonConfig and to read Deployments and Pods in tekton-pipelines, usually a cluster administrator:
-
Edit the TektonConfig resource by setting
spec.pruner.disabledtotrueandspec.tektonpruner.disabledtofalse: -
Wait for the operator to reconcile the changes.
-
Verify that the Deployments and Pods are created: