experimental
experimental copied to clipboard
tektoncd
Experimental Tekton Components
Right now trusted-task only support one key at the same time, we may want to support multiple keys at the same time. One direction is that per verification we try...
- https://github.com/tektoncd/experimental/blob/main/sdk/python/examples/tekton_pipeline_python_sdk_sample.ipynb ``` Define a Task and submit from kubernetes import client as k8s_client from tekton_pipeline import V1beta1Task from tekton_pipeline import V1beta1TaskSpec from tekton_pipeline import V1beta1Step # Define the task...
One of the ideas that came out in the Workflow WG is to have the spec support `secrets` as a first class field. Initial support could be for Kubernetes secrets...
Triggers in workflows should provide a less verbose way to configure triggers. For instance, users should not have to setup EventListeners and the TriggerTemplate should be generated from the provided...
Integration test is missing for trusted-task. We can refer to https://github.com/tektoncd/experimental/tree/051a50ab1691f15aa4285b5bca94881afcccce70/task-loops/test and https://github.com/tektoncd/chains/tree/main/test to add tests for trusted task
Workflows should provide a way to specify a pipeline from git by integrating with [TEP-0060](https://github.com/tektoncd/community/blob/main/teps/0060-remote-resource-resolution.md) First step would be a PoC implementation using the Remote Resolution PoC: https://github.com/tektoncd/experimental/pull/806
Bumps [github.com/sigstore/cosign](https://github.com/sigstore/cosign) from 1.5.2 to 1.10.1. Release notes Sourced from github.com/sigstore/cosign's releases. v1.10.1 This release fixes a security issue cosign verify-attestaton --type can report a false positive if any attestation...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
https://github.com/tektoncd/experimental/blob/47f7e63ad4cf6ba54444c54a5cdb644bf21534f9/pipeline/cleanup/cronjob.yaml#L42-L43 The cleanup cron job cleans up pipelinerun from one namespace. If we want to cleanup pipelineruns from multiple namespaces, do we duplicate the cron job?
A SIGSEGV is raised when a Run changes before its child PipelineRun has started because it hasn't a Succeded condition until it starts. Fix #866 # Changes Check nil ConditionSucceeded...
### Feature request This issue tracks the requirements for the cloudevents controller to be in a position to be integrated with Tekton Pipeline as a standalone controller. - [x] #835...
