-Docs @ v0.22.2
-Examples @ v0.22.2
Installation one-liner
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.22.2/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.22.2/interceptors.yaml
Attestation
The Rekor UUID for this release is 24296fb24b8ad77a0f930f513e632de87b322aa71f55d0223274ba1270553b8aec75be52a95e2540
Obtain the attestation:
REKOR_UUID=24296fb24b8ad77a0f930f513e632de87b322aa71f55d0223274ba1270553b8aec75be52a95e2540
rekor-cli get --uuid $REKOR_UUID --format json | jq -r .Attestation | jq .
Verify that all container images in the attestation are in the release file:
RELEASE_FILE=https://storage.googleapis.com/tekton-releases/triggers/previous/v0.22.2/release.yaml
REKOR_UUID=24296fb24b8ad77a0f930f513e632de87b322aa71f55d0223274ba1270553b8aec75be52a95e2540
# Obtains the list of images with sha from the attestation
REKOR_ATTESTATION_IMAGES=$(rekor-cli get --uuid "$REKOR_UUID" --format json | jq -r .Attestation | jq -r '.subject[]|.name + ":v0.22.2@sha256:" + .digest.sha256')
# Download the release file
curl "$RELEASE_FILE" > release.yaml
# For each image in the attestation, match it to the release file
for image in $REKOR_ATTESTATION_IMAGES; do
printf $image; grep -q $image release.yaml && echo " ===> ok" || echo " ===> no match";
done
Changes
Fixes
- 🐛 Change TLS MinVersion to tls.VersionTLS12 in order to make Triggers run on OCP where FIPS enabled (#1521)
Changed TLS MinVersion to tls.VersionTLS12
in order to make Triggers run on Openshift cluster(Where FIPS enabled) as Openshift uses MInTLS as 1.2 for all components
- 🐛 Replace cloudevents resource with task from hub (#1530)
Cloud events pipeline resource was removed from pipelines recently. Triggers E2E tests run against the main branch of pipelines and that the getting-started tutorial still uses this resource, so Triggers e2e tests have been failing.
Misc
- 🔨 Bump golang.org/x/net from 0.1.0 to 0.7.0 (#1529)
Fixes GHSA-69cg-p879-7622
Thanks
Thanks to these contributors who contributed to v0.22.2!
- ❤️ @khrm
- ❤️ @savitaashture
Extra shout-out for awesome release notes:
- 😍 @khrm
- 😍 @savitaashture