How to Build CI/CD Pipelines for a Microservices Applicatio
summary
Explains building CI/CD for microservices on OpenShift using Tekton pipelines to run pipeline steps as containers, push built container images to an image registry, and sync environments declaratively with Argo CD. Claims pipelines use a reusable task library (Tekton Hub), support retries and concurrency, and eliminate maintaining Jenkins servers. Notes concrete problems: API contract/versioning breakages, network cascade failures, harder testing and increased serialization overhead, and that the setup improves deployment speed but not every other cost.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:39Introduction
- 3:28Microservices
- 5:36Benefits of Microservices
- 6:50Why Use Containers
- 7:19Why Do We Use Containers
- 11:00Install Dependencies
- 11:21Expose the Ports
- 15:00Summarize the Challenges Microservices
related talks
29mContinuous Integration and Continuous Delivery Pipelines: Just the Basics
29mCloud Native CD Pipelines with Tekton
34mFrom Code to Deployment: A Deep Dive into Pipelines as Code
49mServerless CI/CD for Kubernetes with Tekton
51mSelf-Healing CI/CD Pipelines with Tekton and ArgoCD
45mImplementing Cloud Native CI/CD
40mMicroservice Continuous Delivery
48mA Fully GitOps CI/CD Pipeline with Tekton and ArgoCD on Kubernetes