Tutorial: Hands-On Intro to Cloud-Native CI/CD with Tekton - Jan Kleinert & Joel Lord, Red Hat

Don’t miss out! Join us at our upcoming events: EnvoyCon Virtual on October 15 and KubeCon + CloudNativeCon North America 2020 Virtual from November 17-20. Learn more at kubecon.io. The conferences feature presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Tutorial: Hands-On Intro to Cloud-Native CI/CD with Tekton - Jan Kleinert & Joel Lord, Red Hat
This hands-on tutorial introduces the key concepts of Tekton, a flexible, Kubernetes-native CI/CD framework that enables the automation of deployments across multiple platforms - including Kubernetes, serverless, and VMs - by abstracting away the underlying details. In this tutorial, participants will: - Learn about fundamental Tekton concepts and benefits and how to use the tkn CLI - Install tasks and learn about task catalogs - Create a pipeline for building, testing, and deploying an application on Kubernetes - Add pipeline resources - Trigger a pipelinerun - Deploy the application using a pipelinerun
Pre-requisites:
Install the following prior to the tutorial:
minikube: kubernetes.io/...
tkn CLI: github.com/tek...
(optional)
VS Code Tekton extension: marketplace.vi...
sched.co/ZemE

[@rashmitrathod6873]

I started learning Tekton today and fortunately come across this excellent video. Very well explained with simplest possible demo to understand Tekton's basic concep. Big Thank you to Jan & Joel for putting efforts in creating this awesome video.

[@andreasbradahl457]

Awesome demonstrations! Very clear and concise for someone completely new to both CI/CD and pipelines.

[@taenyang-de5ig]

good tutorial！

[@aamazingworld2734]

Thanks for the video instruction. Alas, the PipelineResource has been removed as a resource. Can you replace step 7 of the course?

[@avikkundu]

Getting stuck here everytime. Tried on Katacoda as well as in Minikube: `task hello create has not started yet or pod for task not yet available`

[@mfonnta7618]

how did you solve it? I am having the same problem

[@faisalraj6654]

Hi. As new to Tekton, I didn't get what is the role of Steps in 'Task Definition' when running a pipeline? When Pipeline executed @30:00, it showed value that was passed in sequential order but how 'Task definition Steps' comes into the picture? Can anyone please help me understand? I appreciate. Thanks.

[@fromme2111]

What about the deployment/delivery part of "CI/CD"?

[@itlearner1175]

Don't know how to do maven build for a spring boot application as an example

[@peterkimeli4294]

i can help you on that

[@AmitKarpe]

Code: github.com/joellord/handson-tekton

[@ulkaasati8509]

How can I run same pipeline in different namespaces?

[@veeresharadhya1430]

You have to create a new pipeline in that namespace

[@AjayYeluri]

Ran into issue when running 03_multistep.yaml
TaskRun started: hello-run-v5h8r
Waiting for logs to be available...
[write-hello] Preparing greeting
[write-hello] Done!
[say-hello] internal/fs/utils.js:314
[say-hello] throw err;
[say-hello] ^
[say-hello]
[say-hello] Error: ENOENT: no such file or directory, open '/tekton/home/hello.txt'
[say-hello] at Object.openSync (fs.js:498:3)
[say-hello] at Object.readFileSync (fs.js:394:35)
[say-hello] at Object. (/tekton/scripts/script-1-wmz5f:4:22)
[say-hello] at Module._compile (internal/modules/cjs/loader.js:1072:14)
[say-hello] at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10)
[say-hello] at Module.load (internal/modules/cjs/loader.js:937:32)
[say-hello] at Function.Module._load (internal/modules/cjs/loader.js:778:12)
[say-hello] at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
[say-hello] at internal/main/run_main_module.js:17:47 {
[say-hello] errno: -2,
[say-hello] syscall: 'open',
[say-hello] code: 'ENOENT',
[say-hello] path: '/tekton/home/hello.txt'
[say-hello] }
container step-say-hello has failed : [{"key":"StartedAt","value":"2021-09-26T17:25:06.628Z","type":3}]
Looks like steps were not sharing a common environment.
I am running on EKS. Is there separate setup needed for EKS ?