No description
- Go 99.2%
- Shell 0.6%
d55f53a622
Some checks failed
Scorecard supply-chain security / Scorecard analysis (push) Waiting to run
GitHub Actions Security Analysis with zizmor / zizmor (push) Waiting to run
Go coverage / Go coverage (push) Has been cancelled
Go coverage / Upload coverage to Codecov (push) Has been cancelled
ko does not set an image creation timestamp by default, so every published image inherits the base image's, which can predate the actual release by a long margin. Set SOURCE_DATE_EPOCH from the release commit's timestamp before both ko resolve invocations in the run-ko step (release.yaml and release.notags.yaml), per ko's documented handling of that variable. Signed-off-by: Ogulcan Aydogan <ogulcanaydogan@gmail.com> |
||
|---|---|---|
| .agents | ||
| .claude | ||
| .codex | ||
| .cursor | ||
| .github | ||
| .tekton | ||
| cmd | ||
| config | ||
| docs | ||
| examples | ||
| hack | ||
| internal | ||
| optional_config/enable-log-access-to-controller | ||
| pkg | ||
| skills/tekton-pipeline-discovery | ||
| tekton | ||
| test | ||
| vendor | ||
| .envrc.sample | ||
| .gitattributes | ||
| .gitignore | ||
| .golangci.yml | ||
| .ko.yaml | ||
| .pre-commit-config.yaml | ||
| .wokeignore | ||
| .yamllint | ||
| AGENTS.md | ||
| api_compatibility_policy.md | ||
| code-of-conduct.md | ||
| codecov.yml | ||
| CONTRIBUTING.md | ||
| DEVELOPMENT.md | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| Makefile | ||
| OWNERS | ||
| OWNERS_ALIASES | ||
| pipe.png | ||
| README.md | ||
| releases.md | ||
| roadmap.md | ||
| topical-ownership.md | ||
Tekton Pipelines
The Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines.
Tekton Pipelines are Cloud Native:
- Run on Kubernetes
- Have Kubernetes clusters as a first class type
- Use containers as their building blocks
Tekton Pipelines are Decoupled:
- One Pipeline can be used to deploy to any k8s cluster
- The Tasks which make up a Pipeline can easily be run in isolation
- Resources such as git repos can easily be swapped between runs
Tekton Pipelines are Typed:
- The concept of typed resources means that for a resource such as an
Image, implementations can easily be swapped out (e.g. building with kaniko v.s. buildkit)
Want to start using Pipelines
- Installing Tekton Pipelines
- Jump in with the "Getting started" tutorial!
- Take a look at our roadmap
- Discover our releases
Required Kubernetes Version
- Starting from the v0.24.x release of Tekton: Kubernetes version 1.18 or later
- Starting from the v0.27.x release of Tekton: Kubernetes version 1.19 or later
- Starting from the v0.30.x release of Tekton: Kubernetes version 1.20 or later
- Starting from the v0.33.x release of Tekton: Kubernetes version 1.21 or later
- Starting from the v0.39.x release of Tekton: Kubernetes version 1.22 or later
- Starting from the v0.41.x release of Tekton: Kubernetes version 1.23 or later
- Starting from the v0.45.x release of Tekton: Kubernetes version 1.24 or later
- Starting from the v0.51.x release of Tekton: Kubernetes version 1.25 or later
- Starting from the v0.59.x release of Tekton: Kubernetes version 1.27 or later
- Starting from the v0.61.x release of Tekton: Kubernetes version 1.28 or later
Read the docs
The latest version of our docs is available at:
Version specific links are available in the releases page and on the Tekton website.
See our API compatibility policy for info on the stability level of the API.
See our Deprecations table for features that have been deprecated and the earliest date they'll be removed.
Migrating
v1beta1 to v1
Several Tekton CRDs and API spec fields, including ClusterTask CRD and Pipeline
Resources fields, were updated or deprecated during the migration from v1beta1
to v1.
For users migrating their Tasks and Pipelines from v1beta1 to v1, check
out the v1beta1 to v1 migration guide.
v1alpha1 to v1beta1
In the move from v1alpha1 to v1beta1 several spec fields and Tekton CRDs were updated or removed .
For users migrating their Tasks and Pipelines from v1alpha1 to v1beta1, check out the spec changes and migration paths.
Want to contribute
We are so excited to have you!
- See CONTRIBUTING.md for an overview of our processes
- See DEVELOPMENT.md for how to get started
- Deep dive into demystifying the inner workings (advanced reading material)
- Look at our good first issues and our help wanted issues