This tutorial will guide you through:
- Generating your own keypair and storing it as a Kubernetes Secret
- Creating a sample TaskRun
- Retrieving the signature and payload from the signed TaskRun
- Verifying the signature
We'll be creating a TaskRun
, signing it, and storing the signature and the payload as annotations on the TaskRun
itself.
So, no additional authentication should be required!
You can opt to try the tutorial with either of the following key types:
To generate your own encrypted x509 keypair and save it as a Kubernetes secret, install cosign and run the following:
cosign generate-key-pair k8s://tekton-chains/signing-secrets
cosign will prompt you for a password, which will be stored in a Kubernetes secret named signing-secrets in the tekton-chains namespace.
You'll need to make these changes to the Tekton Chains Config:
artifacts.oci.storage=""
You can set these fields by running
kubectl patch configmap chains-config -n tekton-chains -p='{"data":{"artifacts.oci.storage": ""}}'
This tells Chains to use the default tekton
artifact (enabled by default) and disable the OCI
artifact.
To create a simple TaskRun
, run:
$ kubectl create -f https://raw.githubusercontent.com/tektoncd/chains/main/examples/taskruns/task-output-image.yaml
taskrun.tekton.dev/build-push-run-output-image-qbjvh created
Save the name of your TaskRun
as an environment variable:
$ export TASKRUN=<Name of your TaskRun> # Replace with your taskrun name
Then, take the name of the TaskRun
you just created, and wait for it to finish (SUCCEEEDED should be True).
$ kubectl get taskrun $TASKRUN
NAME SUCCEEDED REASON STARTTIME COMPLETIONTIME
build-push-run-output-image-qbjvh True Succeeded 36m 36m
Next, retrieve the signature and payload from the object (they are stored as base64-encoded annotations):
$ export TASKRUN_UID=$(kubectl get taskrun $TASKRUN -o=json | jq -r '.metadata.uid')
$ kubectl get taskrun $TASKRUN -o=json | jq -r ".metadata.annotations[\"chains.tekton.dev/payload-taskrun-$TASKRUN_UID\"]" | base64 --decode > payload
$ kubectl get taskrun $TASKRUN -o=json | jq -r ".metadata.annotations[\"chains.tekton.dev/signature-taskrun-$TASKRUN_UID\"]" | base64 --decode > signature
Finally, we can check the signature with cosign:
$ cosign verify-blob --key cosign.pub --signature ./signature ./payload
Verified OK
Now we have a verifiable record of the TaskRun
!
This diagram shows what you just deployed: