CI/CD, APIs, and Scaling: What Every Cloud Native Developer Needs To Kn...
summary
Shows a concrete pipeline: code -> Tekton triggers -> Kaniko/Buildah builds -> Trivy scans -> images pushed to Quay/Harbor and deployed by Argo CD as GitOps so manifests are the single source of truth, Argo CD’s app controller continuously reconciles Git and clusters. Recommends REST->GraphQL->event-driven progression, uses HPA/KEDA/Knative (and Carpenter/Crossplane/Karmada for nodes and multicluster) to cut idle cost and autoscale; cites a production platform that handled 70 million concurrent viewers as motivation and demos choosing tools from the CNCF landscape.
AI-written summary · about
chapters (15)
- 0:00Cloud native intro
- 4:12API-first development
- 9:48Monolith vs microservices
- 11:36Containers for deployment
- 13:25Why CI is essential
- 16:18CI pipelines with Tekton
- 19:12CD with Argo CD
- 25:50Microservices with APIs
- 26:56API style choices
- 27:38Event-driven resilience
- 29:01Traditional vs Kubernetes scaling
- 31:08HPA autoscaling
- 32:55CNCF scaling tools
- 34:59CNCF landscape
- 37:50Beginner mistakes
related talks
35mCloud Native Development Without the Toil
56m## Developer toolchain the cloud native way
24mFrom Kubernetes to PaaS to Developer Control Planes
46mIn Search of the Perfect Cloud Native Developer Experience
23mCI/CD at Scale: Best practices with AWS DevOps Services
34mChoose Your Own Adventure: The Dignified Pursuit of a Developer Platf...
32mHow To Make Your Application Developers Fall In Love with Kubernetes & Cloud Native Applications
24mUnveiling Cloud Native Operational Excellence (CNOE)