TKN-TASK-VERIFY(1)

📦 version 0.46.2, in nixos 26.05, nixpkgs unstable

✨ TKN-TASK-VERIFY 💅

okay so bestie, welcome to tkn-task-verify — she's the one who verifies a Tekton Task for you 🎀 this is part of the tkn manual, and honestly she's lowkey iconic for a subcommand.

🌸 SYNOPSIS 🌸

tkn task verify

like, that's it. that's the whole vibe. short and slay ✨

🦋 DESCRIPTION 🦋

So what she actually does: she verifies the Tekton Task using a private key file or a KMS reference that you provide. no cap, you just hand her the goods and she does the vibe check 🫶

The key files support ecdsa, ed25519, rsa. periodt. 💅

For KMS, here's the tea — each provider has its own special little URL format:

  • GCP — this should have the structure of gcpkms://projects/<project>/locations/<location>/keyRings/<keyring>/cryptoKeys/<key> where location, keyring, and key are filled in appropriately. Also run "gcloud auth application-default login" to authenticate 🔑
  • Vault — this should have the structure of hashivault://<keyname>, where the keyname is filled out appropriately.
  • AWS — this should have the structure of awskms://[ENDPOINT]/[ID/ALIAS/ARN] (endpoint optional).
  • Azure — this should have the structure of azurekms://[VAULT_NAME][VAULT_URL]/[KEY_NAME].
⚠️ bestie please read the formats carefully — those brackets and slashes are not decorative, they're the whole assignment 😭

💖 OPTIONS 💖

  • --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.
  • -h, --help[=false] — help for verify 🫶
  • -K, --key-file="" — Key file
  • -m, --kms-key="" — KMS key url
  • -o, --output="" — Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
  • --show-managed-fields[=false] — If true, keep the managedFields when printing objects in JSON or YAML format.
  • --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⟩ ].

👑 OPTIONS INHERITED FROM PARENT COMMANDS 👑

these are the family hand-me-downs, she got them from the parent command 💜

  • -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 🌈

Verify a Task signed.yaml:

tkn Task verify signed.yaml -K=cosign.pub or using kms
tkn Task verify signed.yaml
-m=gcpkms://projects/PROJECTID/locations/LOCATION/keyRings/KEYRING/cryptoKeys/KEY/cryptoKeyVersions/VERSION

like, look at her go 😭🔥 first one's with the key file, second one's the KMS route — iykyk.

⭐ SEE ALSO ⭐

and that's the whole page, bestie 🧚 Auto generated by spf13/cobra — yes she was literally birthed by a code generator, and she still ate 💀 source and version vibes live right here with the TKN-TASK-VERIFY(1) footer, mwah 💋 🍓

📦 where this page comes from