TKN-TASK-DESCRIBE(1)
π TKN-TASK-DESCRIBE(1) β¨
okay bestie, welcome to the tkn-task-describe era β this is the manual page for it, and yes it's the whole vibe π
πΈ NAME
tkn-task-describe β literally describes a Task in a namespace, that's the whole thing, no cap π
π¦ SYNOPSIS
tkn task describe
that's it. that's the synopsis. iconic of it honestly β¨
π§ DESCRIPTION
Describe a Task in a namespace π«Ά
like β you have a Task, it lives in a namespace, and this command tells you all about it. main character energy fr fr π
π OPTIONS
here come the flags, bestie, and we are not skipping a single one, because every single one matters πβ¨
--allow-missing-template-keys[=true]β if it's true, then any errors that pop up in templates (y'know, when a field or map key is missing in the template) just get ignored. important: this only applies to thegolangandjsonpathoutput formats, okay? don't come for me if you use it elsewhere π-h,--help[=false]β shows the help fordescribe. classic. love her π-o,--output=""β the output format, and the options are exactly one of these, no substitutions:json,yaml,name,go-template,go-template-file,template,templatefile,jsonpath,jsonpath-as-json,jsonpath-file. pick your fighter π--show-managed-fields[=false]β if it's true, it keeps themanagedFieldswhen it's printing objects inJSONorYAMLformat. that's the whole job π--template=""β a template string, or a path to a template file, that gets used when you're doing-o=go-templateor-o=go-template-file. the template format is golang templates, and yeah, the docs live at β¨http://golang.org/pkg/text/template/#pkg-overviewβ© β
π OPTIONS INHERITED FROM PARENT COMMANDS
these bad boys come from the parent command β not this one's fault, she just inherited them π§¬π
-c,--context=""β the name of the kubeconfig context to use (default:kubectl config current-context) πΈ-k,--kubeconfig=""β the kubectl config file (default:$HOME/.kube/config) π¦-n,--namespace=""β the namespace to use (default: from$KUBECONFIG) β¨-C,--no-color[=false]β disables coloring (default:false). sometimes you just want it plain, and that's valid π
π₯ EXAMPLE
okay so here's how you describe a Task named foo in namespace bar β literally:
tkn task describe foo -n bar
or, if you're feeling efficient and a little lazy (respect):
tkn t desc foo -n bar
same energy, shorter typing, we love a shortcut π«Άβ
π SEE ALSO
tkn-task(1)β go check out the parent, she's the moment π
friendly reminder bestie: every flag above is copied exactly as it is β the brackets, the defaults, the quotes, all of it. don't go freestyling with them π
love u, go describe some Tasks πβ¨π
β Auto generated by spf13/cobra, bestie π
(that's the source, that's the flex, mwah ππ«Ά)
π¦ where this page comes from
- nixos 26.05: tektoncd-cli 0.45.0
- nixpkgs unstable: tektoncd-cli 0.46.2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms