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
Allow users/integrators to pass arbitrary keys/values to the Result.Annotations
and Result.Summary.Annotations fields, by adding the newly created annotations
results.tekton.dev/resultAnnotations and
results.tekton.dev/recordSummaryAnnotations to their PipelineRuns and TaskRuns.
Those annotations can be used to store relevant metadata (e.g. repository name,
Git commit SHA, pull request number among others) along with results into the
database, in order to be used later to retrieve those resources via the API.
The PipelineRun controller now waits until all TaskRuns associated to a PipelineRun are done and up to date in the API server to delete the PipelineRun and consequentially, all TaskRuns in cascade. If the configured grace period to delete objects is very short (useful in larger clusters with high churn) and there's a lag in the controller's work queue, this guarantees that dependent objects (such as TaskRuns) won't be deleted while they're in an intermediate state in the Results API server.
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
-
-Docs @ v0.6.0
-Examples @ v0.6.0
Installation one-liner
Changes
Features
Allow users/integrators to pass arbitrary keys/values to the Result.Annotations
and Result.Summary.Annotations fields, by adding the newly created annotations
results.tekton.dev/resultAnnotations and
results.tekton.dev/recordSummaryAnnotations to their PipelineRuns and TaskRuns.
Those annotations can be used to store relevant metadata (e.g. repository name,
Git commit SHA, pull request number among others) along with results into the
database, in order to be used later to retrieve those resources via the API.
added namespace property to allow Watcher only watch a specific namespace
Kubernetes impersonation headers can be used when authorizing access to Tekton Results APis.
ACTION REQUIRED: The NO_AUTH config parameter was renamed to AUTH_DISABLE
Fixes
Remove reconciler test that failed due to data race conditions. Test logic was previously moved to an e2e test.
Fixes API Server panics when a bearer token with invalid JWT format is passed.
Grant the watcher permission to get, create, and update log records
Fix GetResult to return the standard "record not found" error if the database query does not find a result.
The PipelineRun controller now waits until all TaskRuns associated to a PipelineRun are done and up to date in the API server to delete the PipelineRun and consequentially, all TaskRuns in cascade. If the configured grace period to delete objects is very short (useful in larger clusters with high churn) and there's a lag in the controller's work queue, this guarantees that dependent objects (such as TaskRuns) won't be deleted while they're in an intermediate state in the Results API server.
Misc
Added unique labels to api and watcher services.
ACTION REQUIRED: Config parameters GRPC_PORT and REST_PORT are replaced by a single parameter SERVER_PORT, which handles both gRPC and REST requests.
Docs
Fix the command for redeploying all the result components from the main.
Thanks
Thanks to these contributors who contributed to v0.6.0!
Extra shout-out for awesome release notes:
This discussion was created from the release Tekton Results release v0.6.0 "Tekton Results".
Beta Was this translation helpful? Give feedback.
All reactions