Tekton Demo

Demo Tekton capabilities building, deploying, testing, ... container images.

This repository is part of a training, that would cover Kubernetes cluster deployment, CSI integration, then some integrated registry deployment. At that stage, you need your own Kubernetes cluster running, and a registry allowing for anonymous pull and pushes. Configurations in this repository would assume that registry does not use TLS - though you may change some params in the main Tekton Pipeline, integrating with an https registry.

Requirements

• your own fork of this repository
• a working Docker registry (WARNING: samples would not handle registry authentication! default uses http, though https can be enabled)
• k8s nodes able to pull images from that registry
• cert-manager operator (generating certificate for Tekton EventListener Ingress / not mandatory, could be done in many different ways ...)

Deploy Tekton

$ kubectl apply -f https://github.com/tektoncd/pipeline/releases/download/v0.25.0/release.yaml
$ kubectl apply -f https://github.com/tektoncd/triggers/releases/download/v0.14.2/release.yaml
$ kubectl apply -f https://github.com/tektoncd/triggers/releases/download/v0.14.2/interceptors.yaml
$ kubectl apply -f https://github.com/tektoncd/dashboard/releases/download/v0.17.0/tekton-dashboard-release.yaml
$ kubectl apply -f https://github.com/tektoncd/chains/releases/download/v0.2.0/release.yaml

Patch Assets

• using a namespace other than test-tekton, there would be some changes to make on YAML files, make sure to replace test-tekton with your own namespace name
• make sure to replace github-ci-el.example.com occurences by the FQDN your Ingress Controllers would use, routing requests to Tekton EventListener
• similarily, replace tekton-dashboard.example.com with the FQDN your Ingress Controllers would use serving your Tekton Dashboard
• there's also a Secret in the triggers-github file that should be changed, to whatever token would be configured, on GitHub side, sending webhooks to your Tekton EventListener
• replace mentions of registry.registry.svc.cluster.local:5000 by the address of your container images registry. it is assumed your kubernetes nodes would be able to pull images from it, without authenticating. and that Tekton jobs may push images, without authenticating.
• generate your own key pair (cosign generate-key-pair) then paste your passphrase, public and private keys into tekton/secret-cosign.yaml.

Install Assets

$ kubectl apply -f tekton/dashboard-certificate.yaml
$ kubectl apply -f tekton/dashboard-ingress.yaml
$ kubectl create ns test-tekton
$ kubectl apply -n test-tekton -f tekton/rbac-pipelines.yaml
$ kubectl apply -n test-tekton -f tekton/rbac-triggers.yaml
$ kubectl apply -n test-tekton -f tekton/task-build.yaml
$ kubectl apply -n test-tekton -f tekton/task-deploy.yaml
$ kubectl apply -n test-tekton -f tekton/task-test.yaml
$ kubectl apply -n test-tekton -f tekton/task-retag.yaml
$ kubectl apply -n test-tekton -f tekton/task-scanimage.yaml
$ kubectl apply -n test-tekton -f tekton/task-scanrepo.yaml
$ kubectl apply -n test-tekton -f tekton/task-sign.yaml
$ kubectl apply -n test-tekton -f tekton/secret-cosign.yaml
$ kubectl apply -n test-tekton -f tekton/pipeline-ci.yaml
$ kubectl apply -n test-tekton -f tekton/triggers-certificate.yaml
$ kubectl apply -n test-tekton -f tekton/triggers-github.yaml
$ kubectl apply -n test-tekton -f tekton/triggers-ingress.yaml

Start Jobs Manually

Test build some random docker image (old Nexus3):

$ kubectl apply -n test-tekton -f tekton/taskrun-buildah.yaml

Test full pipeline building your own fork (make sure to set proper git repo and container images registry URL using your own fork and registry):

$ kubectl create -n test-tekton tekton/pipelinerun-docker.yaml

If all goes well, we should see the various steps completing without returning any error, and the PipelineRun acknowledge job was successful:

$ kubectl get pods -n test-tekton
NAME                                                             READY   STATUS        RESTARTS   AGE
build-pipeline-6wnb8-build-6bpn6-pod-f4svw                       0/6     Completed     0          114s
build-pipeline-6wnb8-codescan-wskc7-pod-5bwk8                    0/2     Completed     0          114s
build-pipeline-6wnb8-deploy-pz9gq-pod-sjpnw                      0/2     Completed     0          77s
build-pipeline-6wnb8-imagescan-vf5zr-pod-cb2w5                   0/1     Completed     0          77s
build-pipeline-6wnb8-retag-4r6cz-pod-f8zft                       0/3     Completed     0          36s
build-pipeline-6wnb8-sign-9f8gn-pod-n9b5q                        0/1     Completed     0          26s
build-pipeline-6wnb8-teardown-ccr4t-pod-spxds                    0/2     Completed     0          21s
build-pipeline-6wnb8-test-nnp6p-pod-vv5px                        0/2     Completed     0          52s
demo-151d066ee4cdfa1eabb527d09e2e112317de7acf-5984487669-tjsnh   0/1     Terminating   0          55s
el-github-listener-64d656fccf-p55xv                              1/1     Running       0          68m
$ kubectl get pipelinerun -n test-tekton
NAME                   SUCCEEDED   REASON      STARTTIME   COMPLETIONTIME
build-pipeline-6wnb8   True        Succeeded   2m28s       44s

Start Jobs Automatically

Configure GitHub Webhook on your fork of this repository. Make sure your hook secret matches the one defined in your tekton/triggers-github.yaml, webhook endpoint should be the one defined in tekton/triggers-ingress.yaml, payload content type should be application/json. Disable TLS certificate verification if you are using self-signed certificates (as the defaults would, applying tekton/triggers-certificate.yaml).

Commit and push some changes to your repository. Your Tekton EventListener should receive a notification, triggering creation for some PipelineResources and a PipelineRun, that would scan your code, build an image, deploy a copy locally and run integration tests, scanning the image, re-tag it if all went well then terminate the demo deployment. Hopefully.

Going Further

The step running CI tests could submit its results to some SonarQube server (or equivalent), having such a deployment available.

The step scanning image downloads its database for each job. One may want to deploy a Trivy server, caching that database locally and serving it to tekton scan-image jobs pod.

We could include some additional tasks sample, building binaries and pushing them to some artifactory (eg: Nexus, jFrog Artifactory, ...). While give an example of building container images based on such assets (?)

We may implement continuous deliveries for a given application, granted that the YAML describing its deployment is part of our repository - or eventually another repository - using something like ArgoCD

Among various ways of verifying images authenticity in Kubernetes, we could look into Connaisseur - https://devopstales.github.io/home/k8s-connaisseur/.

Fix Tekton Tasks authenticating against container image registries.