Time-based Pruning (TTL)

Delete completed resources after a specified duration using ttlSecondsAfterFinished.

How It Works

TTL applies to all completed runs (successful and failed). The timer starts when the run finishes.

Basic Configuration

apiVersion: operator.tekton.dev/v1alpha1
kind: TektonConfig
metadata:
  name: config
spec:
  pruner:
    disabled: true  # Must disable job-based pruner
  tektonpruner:
    disabled: false  # Enable event-based pruner
    global-config:
      ttlSecondsAfterFinished: 3600  # Delete after 1 hour

Common TTL Values

Duration	Seconds	Use Case
5 minutes	`300`	Dev/test rapid iteration
1 hour	`3600`	CI pipelines
1 day	`86400`	General workloads
7 days	`604800`	Staging/release
30 days	`2592000`	Production/audit/compliance

Environment-specific TTLs

spec:
  tektonpruner:
    global-config:
      enforcedConfigLevel: namespace
      ttlSecondsAfterFinished: 3600  # Default
      namespaces:
        dev:
          ttlSecondsAfterFinished: 300      # 5 min
        staging:
          ttlSecondsAfterFinished: 86400    # 1 day
        prod:
          ttlSecondsAfterFinished: 2592000

Pipeline-specific TTLs

Use selectors in namespace ConfigMaps for pipeline-specific TTLs:

WARNING

Namespace-level ConfigMaps are outside the TektonConfig lifecycle. If you need to back up or restore Tekton configuration later, save these ConfigMaps separately.

apiVersion: v1
kind: ConfigMap
metadata:
  name: tekton-pruner-namespace-spec
  namespace: my-app
  labels:
    app.kubernetes.io/part-of: tekton-pruner
    pruner.tekton.dev/config-type: namespace
data:
  ns-config: |
    ttlSecondsAfterFinished: 3600
    pipelineRuns:
      - selector:
          matchLabels:
            pipeline-type: release
        ttlSecondsAfterFinished: 604800
      - selector:
          matchLabels:
            pipeline-type: test
        ttlSecondsAfterFinished: 300

Combining TTL with History Limits

History limits override TTL to guarantee minimum retention:

data:
  ns-config: |
    ttlSecondsAfterFinished: 300
    successfulHistoryLimit: 5
    failedHistoryLimit: 10

Result: Runs are deleted after 5 minutes UNLESS they're in the last 5 successful or last 10 failed.

Best Practices

Development: Short TTLs (5-60 min) for rapid iteration
Production: Long TTLs (7-30 days) for audit/compliance
Critical Pipelines: Use selectors for extended retention
Balance: Consider storage costs vs. retention needs

History-based Pruning - Retain N runs regardless of age
Namespace Configuration - Per-environment TTL settings
Resource Groups - Pipeline-specific TTLs via selectors

#Time-based Pruning (TTL)

#TOC

#How It Works

#Basic Configuration

#Common TTL Values

#Environment-specific TTLs

#Pipeline-specific TTLs

#Combining TTL with History Limits

#Best Practices

#Related