Now you can configure and install the tekton pruner using TektonConfig . TektonConfig Pruner Configuration Here is the default configuration: tektonpruner:   disabled: true   global-config:     enforcedConfigLevel: global     failedHistoryLimit: null     historyLimit: 100     successfulHistoryLimit: null     ttlSecondsAfterFinished: null   options: {} Enabling Tekton Pruner Tekton Pruner is now available as part of TektonConfig. You can manage its settings under the tektonpruner section. TektonPruner is disabled by default and to enable Tekton Pruner, set disabled to false in the tektonpruner section of your TektonConfig: At the same time you also need to disable the older pruner. Both pruners cannot be enabled at the same time. pruner:   disabled: true   tektonpruner:   disabled: false If you try to enable both pruners, you will encounter an error during installation. 🔧 Customizing History Retention You can fine-tune pruning behavior by modifying the following fields under global-config: historyLimit: Maximum number of failed and successful runs to retain. This field is shorthand for defining same value for failedHistoryLimit and successfulHistoryLimit. failedHistoryLimit: Number of failed runs to retain. successfulHistoryLimit: Number of successful runs to retain. ttlSecondsAfterFinished**: Time (in seconds) to retain completed runs before pruning. You can specify any combination of these fields. The pruner deletes runs when any one of the specified conditions is met. Example: global-config:   ttlSecondsAfterFinished: 3600   historyLimit: 100 This configuration deletes the runs if: They are older than 1 hour, OR There are more than 100 successful runs, OR There are more than 100 failed runs