tkn customrun describe describes a CustomRun

Introduced 2026-05-12 · score 0.96

HOW TO USE IT

When debugging a Tekton pipeline run, describe the target CustomRun with `tkn customrun describe <name> -n <namespace>`; use `--fzf` to select one, `--last` for the last CustomRun, or `--limit <count>` to set the number listed during selection.

WHY THIS HELPS

Inspect a CustomRun while debugging a Tekton pipeline run.

REQUIREMENTS AND LIMITATIONS

• Version: v0.45.0
• <name> (required): Name of the CustomRun to describe.
• -n, --namespace <namespace>: Namespace to use; default is from KUBECONFIG.
• -F, --fzf: Use fzf to select a CustomRun to describe.
• -L, --last: Show description for the last CustomRun.
• --limit <int>: Number of CustomRuns listed when selecting; default 5.
• -o, --output <string>: Output format: json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, or jsonpath-file.
• --template <string>: Template string or file path when output is go-template or go-template-file.
• --show-managed-fields: Keep managedFields when printing JSON or YAML.
• --allow-missing-template-keys: Ignore template errors for missing fields or map keys; applies only to golang and jsonpath output formats; default true.
• -c, --context <string>: Name of kubeconfig context; defaults to kubectl current-context.
• -k, --kubeconfig <string>: kubectl config file; default is $HOME/.kube/config.
• -C, --no-color: Disable coloring; default false.
• The command describes a CustomRun in a namespace.
• `--limit` applies when selecting a CustomRun to describe and defaults to 5.
• `--output` supports the formats listed in the source.

FIRST-PARTY EVIDENCE

• https://github.com/tektoncd/cli/releases/tag/v0.45.0
• https://github.com/tektoncd/cli/pull/2712
• https://github.com/tektoncd/cli/blob/v0.45.0/docs/cmd/tkn_customrun_describe.md

Check the installed version and the source before using it. Entry JSON

Report a problem with this card