## TL;DR

Describe the PipelineRun to find the failed TaskRun (kubectl get taskruns with the pipelineRun label), then get the step logs with kubectl logs on the pod with -c step plus the failed step name, then kubectl get events in the namespace.

## The error

```text
debugging a failed PipelineRun - standard kubectl recipe
```

## Fix

1. Describe the PipelineRun to find the failed TaskRun (kubectl get taskruns with the pipelineRun label), then get the step logs with kubectl logs on the pod with -c step plus the failed step name, then kubectl get events in the namespace.
   Expected: you can confirm this matches your situation.
2. Re-run the original operation and confirm the error is gone.
   Expected: no error, normal output.

## When to use

- You hit this exact error with Tekton.
- The symptom matches: debugging a failed PipelineRun - standard kubectl recipe.

## When NOT to use

- A different error message from Tekton; the cause here is specific to this error.
- Unrelated Tekton issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Tekton. Source: https://github.com/konflux-ci/agent-plugins/blob/HEAD/skills/debugging-pipeline-failures/README.md.

## Variant phrasings

### debugging a failed PipelineRun - standard kubectl recipe

## Why it happens

A PipelineRun failed and you need the standard triage sequence.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.

## Source

https://github.com/konflux-ci/agent-plugins/blob/HEAD/skills/debugging-pipeline-failures/README.md