The Kubernetes hitchhiker's guide to CI/CD
summary
Kubernetes is used to provide per-branch staging by creating a namespace for each pull request and deleting it after merge. A Jenkins pipeline clones the repo, runs composer tests inside a container, builds and tags a Docker image, pushes it to Docker Hub, then triggers a Helm release to deploy services, ConfigMaps, Ingress and jobs into the new namespace; speaker notes demos can be flaky and production clusters need multiple masters and many nodes to scale.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:15Why Kubernetes for dev
- 10:15Laravel on Kubernetes
- 17:46Automating staging with Jenkins
- 23:23Live demo: staging setup
- 30:32CI/CD benefits & Q&A
related talks
35mJenkins X: Easy CI/CD for Kubernetes
50mContinuous Deployment With Jenkins X And Kubernetes
38mUsing Containers for Continuous Integration and Continuous Delivery [I]
50mKubernetes First Continuous Delivery for Developers
35mOff the Beaten Path: An Explorer’s Guide to Kubernetes
39mAccelerate your CI/CD on Kubernetes with Jenkins X
26mCI/CD with Kubernetes - the Good, the Bad and the Ugly
52mAdding containers to your CI/CD pipeline