Tekton Pipeline Run High Failure Rate

TektonPipelineRunHighFailureRate #

Meaning #

The PipelineRun failure rate on Tekton has exceeded the 80% SLO threshold. More than 20% of PipelineRuns are failing.

Impact #

CI/CD pipelines are failing at an elevated rate. New code changes may not be built, tested, or deployed.

Diagnosis #

Check Tekton controller status:

kubectl get pods -n tekton-pipelines -l app.kubernetes.io/part-of=tekton-pipelines

List recent failed PipelineRuns:

kubectl get pipelineruns -n tekton-pipelines --sort-by=.metadata.creationTimestamp | tail -20

Check logs for a specific failed PipelineRun (replace ${pipelinerun} with the name from above):

kubectl logs -n tekton-pipelines ${pipelinerun}

Check webhook connectivity if pipelines are triggered by webhooks:

kubectl get pods -n tekton-pipelines -l app.kubernetes.io/part-of=tekton-triggers

Mitigation #

Investigate the specific failing pipelines by checking task step logs. If the controller is unhealthy, restart it:

kubectl rollout restart deployment -n tekton-pipelines tekton-pipelines-controller

Check cluster resources (CPU, memory, storage) if tasks are failing due to resource constraints.