Case Study Conrad Electronic – From a Static Infrastructure to Continuous Delivery and the Cloud in One Step [B]
summary
Conrad migrates development to Google Cloud and GKE, building a CI/CD pipeline where a Bitbucket button triggers Jenkins to build images, push to Google Container Registry and deploy per-branch Kubernetes namespaces with automatic load balancers and DNS; namespaces auto-scale and are torn down nightly to save cost. Pipeline integrates VPN-restricted access, automated OpenVPN provisioning in Docker, a local registry mirror, and about ~20 services; large AEM 100–200 GB images remain a pain. Dev workflows and testing speed up; production stays on separate infrastructure for now.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:38Where all this comes from
- 2:38The process
- 9:44Network setup
- 11:56Cluster setup
- 14:00Delivery pipeline
- 16:36Demo
- 24:27Network Connectivity
- 24:45Network Alignment
- 25:14APM is Pain
- 25:54Adobe Enterprise Content Manager
- 26:59Open VPN
- 28:18Local Repository
- 29:57Container Engine
- 31:53Jenkins
- 37:41Hotfix
related talks
44mContainers and CI/CD on Google Cloud
38mBuilding a Cloud Native Culture in an Enterprise - Deep Kapadia & Tony Li
01h 06mon
42mAutomation, Innovation and Continuous Delivery
39mAutoScaling CI infrastructure on Google Container Engine
28mWith Docker and k8's, this is not your grandparents' infra anymore!
28mAutomate Everything
01h 02mThe Road to continuous deployment