You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Verify that all container images in the attestation are in the release file:
RELEASE_FILE=https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.53.0/release.yaml
REKOR_UUID=24296fb24b8ad77ae1d898a8665e246adf87237e426dcb51e61a4f34dfda16ed10148ce5c80c57df
# 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.53.0@sha256:" + .digest.sha256')# Download the release file
curl "$RELEASE_FILE"> release.yaml
# For each image in the attestation, match it to the release fileforimagein$REKOR_ATTESTATION_IMAGES;doprintf$image; grep -q $image release.yaml &&echo" ===> ok"||echo" ===> no match";done
Upgrade Notices
[TEP-0104] Task-level Resource Requirements in now beta
Matrix is now beta
Starting with this release, all new API driven features will be controlled by individual feature flags, and the enable-api-fields flag will be eventually phased out, once all API features currently in alpha/beta reach stability (or are removed)
Add special value * to the blocked-namespace setting for the cluster-resolver to disallow by default all namespaces and only allow the namespaces explicitly listed in allowed-namespace setting.
The task-level resource requirements feature allows the user to set computeResources at runtime i.e. on TaskRun. This is now enabled as part of the beta API.
Pipeline authors can now produce results from a Matrixed PipelineTask as an aggregated array and consume them in an array params. Two context variables are introduced as part of this feature, $(tasks..matrix.length) to get the length of a matrix combinations and $(tasks..matrix..length) to get a length of aggregated result.
Add ability to include reason along with status in TaskRun and PipelineRun count metrics
Backwards incompatible changes
In the current release:
🚨 The behaviour of the enable-api-field flag has been fixed, resulting in a slight behaviour change: when using the v1beta1 API, API features in beta are only available when the enable-api-field is set to beta or alpha. Beta features used to be enabled on the v1beta1 API regardless of the value of enable-api-field.
Note that:
The default value for enable-api-field is beta
Users that have the flag set to alpha or beta will continue to have access to beta features on v1beta1 and v1 APIs
Users that have the flag set to stable will continue to not have access to beta features on the v1 API
So in practice, there is no breaking change for users. Users of the v1beta1 API may now disable beta features, should they wish to do so, which was not possible before.
Change configmap for LeaderElection of webhook to config-leader-election-webhook, event controller to config-leader-election-event and resolvers to config-leader-election-resolvers
v1beta1 CRDs with beta features now requires betaenable-api-fields. More specifically, users who have been accidentally using beta features resolvers, object array params and results with enable-api-fields set to stable now needs to change to enable-api-fields=beta
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
🎉 CEL-based when expressions, Results from Matrices, beta promotions and more 🎉
-Docs @ v0.53.0
-Examples @ v0.53.0
Installation one-liner
Attestation
The Rekor UUID for this release is
24296fb24b8ad77ae1d898a8665e246adf87237e426dcb51e61a4f34dfda16ed10148ce5c80c57df
Obtain the attestation:
Verify that all container images in the attestation are in the release file:
Upgrade Notices
enable-api-fields
flag will be eventually phased out, once all API features currently in alpha/beta reach stability (or are removed)Changes
Features
displayName
#7273)displayName
can now accept params, task result references, or context variables.hub resolver can now specify a version constraint to choose a version (example: version: ">=0.2.0,< 1.0.0")
tekton resolver now uses hub.tekton.dev by default.
✨ [TEP-0145] Add CEL field to WhenExpression
Support CEL expression in WhenExpression to guard the execution of Tasks
✨ Add a setting disallowing access to all namespaces (Add a setting disallowing access to all namespaces #7237)
Add special value
*
to the blocked-namespace setting for the cluster-resolver to disallow by default all namespaces and only allow the namespaces explicitly listed inallowed-namespace
setting.The task-level resource requirements feature allows the user to set computeResources at runtime i.e. on TaskRun. This is now enabled as part of the beta API.
Pipeline authors can now produce results from a Matrixed PipelineTask as an aggregated array and consume them in an array params. Two context variables are introduced as part of this feature,$(tasks..matrix.length) to get the length of a matrix combinations and $ (tasks..matrix..length) to get a length of aggregated result.
Matrix feature is promoted to beta and possible to utilize with enable-api-fields set to beta.
Results are propagated in embedded specifications without mutations.
Please use per feature flags for new API-driven feature gating.
Add ability to include
reason
along withstatus
in TaskRun and PipelineRun count metricsBackwards incompatible changes
In the current release:
🚨 The behaviour of the
enable-api-field
flag has been fixed, resulting in a slight behaviour change: when using thev1beta1
API, API features in beta are only available when theenable-api-field
is set tobeta
oralpha
. Beta features used to be enabled on thev1beta1
API regardless of the value ofenable-api-field
.Note that:
enable-api-field
isbeta
alpha
orbeta
will continue to have access tobeta
features onv1beta1
andv1
APIsstable
will continue to not have access tobeta
features on thev1
APISo in practice, there is no breaking change for users. Users of the
v1beta1
API may now disablebeta
features, should they wish to do so, which was not possible before.Work-in-progress
enable-step-actions
#7277)[WIP] Introduces a new feature flag "enable-step-actions: true/false" to gate the use of step actions.
Introduced the StepAction CRD as designed in https://github.com/tektoncd/community/blob/main/teps/0142-enable-step-reusability.md. The implementation is still ongoing; feature is not yet functional.
Fixes
Fix regression where a different order of task definition may cause result resolution to break
Bug fix: delete PVCs created by VolumeClaimTemplates when the owning PipelineRun is completed
Recover Conversion Functions from Pipeline Resources for backwards compatibility
Change configmap for LeaderElection of webhook to config-leader-election-webhook, event controller to config-leader-election-event and resolvers to config-leader-election-resolvers
Misc
refactor: version.ValidateEnabledAPIFields has been moved to the config package
v1beta1 CRDs with beta features now requires
beta
enable-api-fields
. More specifically, users who have been accidentally using beta features resolvers, object array params and results withenable-api-fields
set tostable
now needs to change toenable-api-fields=beta
cmp.Diff
to follow the(want, got)
pattern #7027 Cleanupcmp.Diff(want, got)
for alldiff.PrintWantGot()
(#7027 Cleanupcmp.Diff(want, got)
for alldiff.PrintWantGot()
#7209)Docs
Thanks
Thanks to these contributors who contributed to v0.53.0!
Extra shout-out for awesome release notes:
This discussion was created from the release Tekton Pipeline release v0.53.0 "Munchkin Maschinenmensch" LTS.
Beta Was this translation helpful? Give feedback.
All reactions