TKN-PIPELINERUN-DESCRIBE(1)

📦 version 0.46.2, in nixos 26.05, nixpkgs unstable

✨ NAME ✨

okay bestie, so this is tkn-pipelinerun-describe(1) — the page that tells you how to Describe a PipelineRun in a namespace. that's it, that's the whole vibe 💅

🌸 SYNOPSIS 🌸

tkn pipelinerun describe

like yes, that's literally the whole invocation, she's lowkey simple 🎀

🦋 DESCRIPTION 🦋

Describe a PipelineRun in a namespace.

fr fr, that's what it does — you point it at a PipelineRun and it spills all the tea about it. no cap. ✨

👑 OPTIONS 👑

okay this is the part you actually came for, so buckle up buttercup 🫶

  • --allow-missing-template-keys[=true] — If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. so like, template errors? not today bestie 🙈
  • -F, --fzf[=false] — use fzf to select a PipelineRun to describe. interactive queen behavior 💅
  • -h, --help[=false] — help for describe. the classic "wait what does this do again" button 😭
  • -L, --last[=false] — show description for last PipelineRun. the most recent one, the main character of the pipeline world 👑
  • --limit=5 — lists number of PipelineRuns when selecting a PipelineRun to describe. default is 5, so you get a cute little menu of five 🍓
  • -o, --output="" — Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). pick your format, pick your fighter ⭐
  • --show-managed-fields[=false] — If true, keep the managedFields when printing objects in JSON or YAML format. yes the managedFields, they're staying, they're iconic 💜
  • --template="" — Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [ ⟨http://golang.org/pkg/text/template/#pkg-overview⟩ ]. go off with your golang templates 🧚

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

these ones you didn't even have to ask for, they come with the family 🎀

  • -c, --context="" — name of the kubeconfig context to use (default: kubectl config current-context). so it just knows where you are, iykyk 🌸
  • -k, --kubeconfig="" — kubectl config file (default: $HOME/.kube/config). the classic spot 💖
  • -n, --namespace="" — namespace to use (default: from $KUBECONFIG). where the magic happens ✨
  • -C, --no-color[=false] — disable coloring (default: false). for when you're feeling monochrome, no judgement 🦋

💀 EXAMPLE 💀

Describe a PipelineRun of name 'foo' in namespace 'bar':

tkn pipelinerun describe foo -n bar

or

tkn pr desc foo -n bar

see what she did there? pr desc is the short lil nickname, because typing is hard and we're busy 🫶

🔥 SEE ALSO 🔥

and that's the whole page bestie, you ate that 🍓

Auto generated by spf13/cobra — yeah the robots wrote this one, so shoutout to spf13/cobra for the assist, mwah 💋 and that's the TKN-PIPELINERUN-DESCRIBE(1) page, signing off 🎀✨💅

📦 where this page comes from