k8sci Documentation

Contents

• Tekton Dependencies
• Other Dependencies
• Contributing
• Pipelines
• Git commit statuses(:name=git-commit-statuses)
• Pipeline Secrets
  • git ssh config
• Pipeline Examples
• Ingress Config and Webhooks
• Git Sources
• Dashboard Ingress
• Webhook Endpoints
• Configuring a gitub/gitea webhooks
• Examples
  • a simple golang pipeline
  • a pipeline for helm charts
  • a pipeline that runs github actions

Tekton dependencies

Managing crd dependencies, which are not templated, in a helm chart can be tricky.

This chart uses and includes crds, which are the versioned release files supplied by tekton pipeline tekton trigger and tekton dashboard. Since tekton releases often and sometimes with breaking changes we pin a k8sci release to specific versions of tekton pipelines, tekton triggers and tekton dashboard. The specific crd files are included in the crds directory with the version appended as a file name suffix. Please note that deleting this chart will not remove the dependencies since they are not templated. Also changing the version of the CRDs outside of the chart risks breaking it. Finally please note that the tekton CRDs install resources in specific namespaces.

Installing the helm chart will automatically apply the crds. The tekton crd releases are included in the crds folder and may also be applied manually:

kubectl apply -f ./crds

Other dependencies

In order to process gitea webhooks Tekton requires a specialized interceptor. We built a gitea interceptor for tekton triggers. k8sci uses the image built from this project.