TKN-PIPELINERUN-LOGS(1)

πŸ“¦
version 0.46.2 Β· 2 versions
, in nixpkgs unstable

πŸ’… tkn-pipelinerun-logs β€” aka the tkn pipelinerun logs page

okay so this is the manual page for tkn-pipelinerun-logs, part of the tkn fam 🫢 β€” it's the one that shows you the logs of a PipelineRun. yes bestie, the actual scroll-y stuff your pipeline is screaming into the void. let's get into it ✨


🌸 NAME 🌸

tkn-pipelinerun-logs β€” Show the logs of a PipelineRun


πŸŽ€ SYNOPSIS πŸŽ€

tkn pipelinerun logs

that's it, that's the vibe πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

Show the logs of a PipelineRun. iconic, honestly. you point it at a PipelineRun and it hands you the logs. no cap, that's the whole gig πŸ”₯


✨ OPTIONS ✨

  • -a, --all[=false] β€” show all logs, including the init steps that tekton injects πŸ‘€ (by default it's false, so those sneaky init steps stay hidden)
  • -E, --exit-with-pipelinerun-error[=false] β€” exits with the pipelinerun's status into the unix shell: 0 if success, 1 if error, 2 on unknown status. so your scripts can vibe-check the whole thing 😭
  • -f, --follow[=false] β€” stream live logs ⭐ literally watching them roll in, main character energy
  • -F, --fzf[=false] β€” use fzf to select a PipelineRun 🧚 (yes, the fuzzy finder, we love her)
  • -h, --help[=false] β€” help for logs 🫢
  • -L, --last[=false] β€” show logs for the last PipelineRun πŸ‘‘ the most recent one, no scrolling required
  • --limit=5 β€” lists number of PipelineRuns. default is 5, okay? five. don't come for me
  • --log-failed[=false] β€” show logs for failed tasks only πŸ’€ (when you only care about the chaos)
  • --long[=false] β€” show logs with task display name (display name and step name) πŸŽ€
  • --prefix[=true] β€” prefix each log line with the log source (task name and step name). default is true, and honestly thank her, otherwise it's soup 🌈
  • -t, --task=[] β€” show logs for the mentioned Tasks only. it's a list, default empty []
  • --timestamps[=false] β€” show logs with timestamp ⭐ so you know exactly when things went sideways

πŸ’œ OPTIONS INHERITED FROM PARENT COMMANDS πŸ’œ

these come from the parent command, so you get them for free, bestie 🫢

  • -c, --context="" β€” name of the kubeconfig context to use (default: kubectl config current-context)
  • -k, --kubeconfig="" β€” kubectl config file (default: $HOME/.kube/config)
  • -n, --namespace="" β€” namespace to use (default: from $KUBECONFIG)
  • -C, --no-color[=false] β€” disable coloring (default: false)

🌺 EXAMPLE 🌺

Show the logs of PipelineRun named 'foo' from namespace 'bar':

tkn pipelinerun logs foo -n bar

Show the logs of PipelineRun named 'microservice-1' for Task 'build' only from namespace 'bar':

tkn pr logs microservice-1 -t build -n bar

Show the logs of PipelineRun named 'microservice-1' for all Tasks and steps (including init steps) from namespace 'foo':

tkn pr logs microservice-1 -a -n foo

Show the logs of PipelineRun named 'microservice-1' for failed Tasks only from namespace 'bar':

tkn pr logs microservice-1 --log-failed -n bar

see? four examples, all exact, all slaying πŸ’…


πŸ“ SEE ALSO πŸ“


ngl the whole page is auto generated by spf13/cobra, so like… the robots wrote the skeleton, i just gave it a personality 🧚✨

and that's a wrap, bestie β€” source: auto generated by spf13/cobra, version/manual: TKN-PIPELINERUN-LOGS(1), date: none printed on the page πŸ™ˆ (no date stamp was given, so I'm not making one up). go read some logs, you got this πŸ‘‘πŸ’–

πŸ“¦ where this page comes from