This document discusses when to use Kubernetes-native CI/CD tools like Tekton instead of traditional CI/CD servers. It introduces Tekton as an open-source framework for building reusable CI/CD pipelines that runs on Kubernetes. The key benefits of Kubernetes-native tools are centralized logging and monitoring, high availability guaranteed by Kubernetes, and self-healing capabilities. The document suggests considering Kubernetes-native CI/CD when your workloads are already running on Kubernetes.

1. Kubernetes-native or not?
When to ditch your traditional CI/CD server?
Dewan Ahmed
Software Quality Engineer
@DewanAhmed

2. Agenda
The challenges with existing CI/CD tools
What is Tekton?
Tekton concepts
Tekton sub-projects
When to choose a Kubernetes-native CI/CD?
Demo
Q/A

4. What is Tekton?
● An open-source framework for
creating reusable CI/CD systems
● Started off as Knative Build project
● Runs on Kubernetes
● Uses CRDs to extend Kubernetes

5. Tekton Concepts
Tekton Concepts

6. Tekton Sub-
projects
Pipelines
Triggers
Dashboard
CLI
Catalog
… and more

7. When to choose a K8s-native CI/CD server?
Are you using Kubernetes?

8. Challenges around traditional CI/CD servers
Traditional CI/CD Server Kubernetes-native CI/CD Server
Logging and monitoring is on an external agent Centralized logging and monitoring
High-availability is not possible or complex to
achieve
The platform guarantees high-availability
Self-healing is not possible (retry logic for some
tools)
Self-healing comes by default
Most CI/CD servers are from a pre-container era Runs as containers on Kubernetes

9. Demo Time

10. Thank you
Getting Started with Tekton
Tekton Website: tekton.dev
Tekton GitHub Repo: https://github.com/tektoncd
Tekton Public Slack: https://tektoncd.slack.com
RHD Tekton Tutorial: https://dn.dev/tekton-tutorial
@DewanAhmedlinkedin.com/in/diahmed