TKN-CUSTOMRUN-LIST(1)

πŸ“¦ version 0.46.2, in nixos 26.05, nixpkgs unstable

πŸ’… TKN-CUSTOMRUN-LIST(1) β€” bestie's guide to listing CustomRuns ✨

okay so you found the tkn-customrun-list page, and honestly? iconic of you. this is the man page for tkn-customrun-list, and it's about to be your new fave. let's go 🫢

🌸 NAME 🌸

tkn-customrun-list β€” literally lists CustomRuns in a namespace. that's the whole vibe. no cap.

✨ SYNOPSIS ✨

tkn customrun list

that's it. that's the command. short, sweet, main character energy πŸ‘‘

πŸ¦‹ DESCRIPTION πŸ¦‹

Lists CustomRuns in a namespace. yes bestie, that's the entire description in the original too β€” the man page is being mysterious and lowkey minimal about it. we respect it πŸ’…

πŸŽ€ OPTIONS πŸŽ€

  • -A, --all-namespaces[=false] β€” bestie, this one goes everywhere. it lists CustomRuns from all namespaces instead of just one. so much range 🌈
  • --allow-missing-template-keys[=true] β€” if true, it just ignores any errors in templates when a field or map key is missing in the template. like forgiving your group chat for leaving you on read 😌. heads up though: this only applies to golang and jsonpath output formats. don't forget that part, iykyk.
  • -h, --help[=false] β€” help for list. the classic "wait what does this do again" button 🧚
  • --label="" β€” a selector (label query) to filter on. it supports =, ==, and !=. so you can be picky about which CustomRuns you hang out with πŸ’–
  • --limit=0 β€” limits the number of CustomRuns. if the limit value is 0 it returns all of them. zero means everything, which is honestly such a mood.
  • --no-headers[=false] β€” do not print column headers with output. btw the default is to print column headers with output, so this flag is you saying "i already know what the columns are, bestie" πŸ™ˆ
  • -o, --output="" β€” output format! one of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). pick your fighter ⭐
  • --reverse[=false] β€” list CustomRuns in reverse order. for when you wanna read the timeline backwards, no judgement πŸ’€
  • --show-managed-fields[=false] β€” if true, keep the managedFields when printing objects in JSON or YAML format. only relevant for the JSON/YAML girlies πŸ’œ
  • --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⟩ ]. fancy fancy πŸŽ€

πŸ‘‘ OPTIONS INHERITED FROM PARENT COMMANDS πŸ‘‘

these come from the parent command, so you get them for free. slay.

  • -c, --context="" β€” name of the kubeconfig context to use (default: kubectl config current-context). it knows where you are fr fr.
  • -k, --kubeconfig="" β€” kubectl config file (default: $HOME/.kube/config). your config's home base 🏠
  • -n, --namespace="" β€” namespace to use (default: from $KUBECONFIG). the lil zone you're working in ✨
  • -C, --no-color[=false] β€” disable coloring (default: false). turn the sparkle OFF if you must 🌸

πŸ”₯ EXAMPLE πŸ”₯

List all CustomRuns in namespace 'bar':

tkn cr list -n bar

see how it's cr instead of customrun? shorthand ate. πŸ’…

🌈 SEE ALSO 🌈

  • tkn-customrun(1) β€” go read the parent page too, bestie, it's giving family reunion 🫢

ngl that's the whole page. every flag, every default, every value β€” nothing skipped, because you deserve the full tea πŸ“

kisses and kubectl configs πŸ’œ β€” this iconic little number was auto generated by spf13/cobra (yes, really, it wrote itself, main character behavior), and it's the TKN-CUSTOMRUN-LIST(1) page, so go forth and list those CustomRuns βœ¨πŸŽ€πŸ’–

πŸ“¦ where this page comes from