debugging-pipeline-failures

Debugging Konflux pipeline failures involves a systematic 5-phase approach: identify the failed PipelineRun or TaskRun component, analyze logs using kubectl logs, correlate Kubernetes events, inspect resource state (CPU, memory, quotas), and perform root-cause analysis. Use kubectl describe pipelinerun, kubectl logs, and kubectl get events to retrieve diagnostic data across phases.

ImagePullBackOff occurs when container images cannot be pulled due to registry access or image availability issues. Resource quota errors happen when TaskRuns exceed allocated CPU, memory, or PVCs. This Skill guides you through kubectl commands to inspect PipelineRun events, check namespace quotas, and identify OOMKilled or quota-exceeded conditions triggering pipeline timeouts or failures.

Yes. Stuck or timed-out pipelines are diagnosed by correlating PipelineRun and TaskRun status, examining kubectl events and logs, and inspecting workspace or permission issues. Standard kubectl tooling and the Tekton CLI retrieve resource details, event timelines, and step-by-step logs needed to pinpoint whether delays stem from resource constraints, workspace misconfiguration, or permission denials.

Root-cause analysis follows a disciplined 5-phase investigation: identify the failed component within the PipelineRun, analyze logs from affected TaskRuns, correlate Kubernetes events for timing and error patterns, inspect resource state (memory, CPU, quotas, PVCs), and synthesize findings into actionable remediation steps. This Skill provides command cheat-sheets and common failure patterns to accelerate diagnosis.

Workspace misconfigurations or insufficient permissions can cause TaskRun failures or hangs. This Skill helps you inspect workspace mounts, verify ServiceAccount permissions, and correlate permission-related errors in kubectl events and logs to resolve access barriers preventing pipeline progression or task completion.

Standard Kubernetes and Tekton tooling suffice: kubectl (describe, logs, get events commands), the Tekton CLI, and log and event correlation techniques. This Skill requires no additional dependencies—it teaches how to use kubectl and Tekton commands to retrieve PipelineRun state, TaskRun logs, and Kubernetes events for systematic failure diagnosis.