Skip to content

Tekton Triggers release v0.29.0 "Tekton Triggers LTS"

Compare
Choose a tag to compare
@tekton-robot tekton-robot released this 21 Aug 09:56

-Docs @ v0.29.0
-Examples @ v0.29.0

Installation one-liner

kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.29.0/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.29.0/interceptors.yaml

Attestation

The Rekor UUID for this release is 108e9186e8c5677ad076cc4e98758a3298fe82176ab9bd6ab7d90e9ae59a0ccc9104b0d7ae540aa4

Obtain the attestation:

REKOR_UUID=108e9186e8c5677ad076cc4e98758a3298fe82176ab9bd6ab7d90e9ae59a0ccc9104b0d7ae540aa4
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.29.0/release.yaml
REKOR_UUID=108e9186e8c5677ad076cc4e98758a3298fe82176ab9bd6ab7d90e9ae59a0ccc9104b0d7ae540aa4

# 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.29.0@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

Features

  • ✨ Add new flag set-read-only-root-filesystem to set readOnlyRootFilesys… (#1742)

Added a new flag el-read-only-root-filesystem to the tekton-triggers-controller container. This flag, which is set to true by default, configures the EventListener container's securityContext.readOnlyRootFilesystem to true. This change aligns with Azure AKS best practices and enhances security.

  • ✨ Update eventlistener podSeurityContext to adhere to restricted pod security (#1740)

Eventlistener podTemplate now includes securityContext settings: seccompProfile, runAsUser, runAsGroup, and fsGroup when flag el-security-context is true.

Breaking Changes

  • 🚨 Metric name for eventlistener is changed from eventlistener_event_count
    to eventlistener_event_received_count (#1755)

Misc

  • 🔨 Install latest pipeline release in tests (#1758)

Install latest pipeline release in tests

  • 🔨 Bump Pipelines to v0.62.1 (#1754)

Bump Pipelines to v0.62.1

  • 🔨 Add runAsUser and runAsGroup under setSecurityContext flag (#1756)

Docs

  • 📖 Remove duplicate Triggers reference from TriggerGroup section of documentation (#1757)

Updated Documentation on TriggerGroups

  • 📖 Updated URL's on eventlisteners.md (#1750)
  • 📖 fix(example): update default branch name in examples (#1748)
  • 📖 Fixes eventlistener link and cel expression yaml example in docs (#1746)

Thanks

Thanks to these contributors who contributed to v0.29.0!

Extra shout-out for awesome release notes: