Lessons Learned Deploying Traditional Web Applications on Top of Kubernetes
summary
Bitnami deploys almost 100 traditional apps and over 20 are Helm-deployable; workflow is: build OCI images (multi-stage to shrink size), package Helm subcharts, and run CI/CD to publish images and charts. Practical rules: run containers as arbitrary UID with nss_wrapper, set writable paths at build time, persist only runtime data, backup DB and scale to one before upgrades. Example: a WordPress image shrinks from ~1.5GB to under 0.75GB with these techniques.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:20Traditional Web Applications
- 3:46General Workflow for a Traditional Web Application What processes and steps are required to deploy on Kubernetes
- 4:17Build Container Image
- 6:39Build Helm Chart
- 7:58Build and Release Pipeline What steps to perform on a build and release pipeline
- 12:15Optimize Container Image Size How to reduce your container image size
- 14:22Good practices
- 17:17Persistence of Application Data What application les to persist between runs
- 20:22Multiple Application Services How to support running multiple application services
- 22:13Horizontal Scaling How to design a Helm chart to support scaling your application updown
- 26:47WordPress deployment on Kubernetes
related talks
43mTaking the Helm: Delivering Kubernetes-Native Applications
30mScaling to 5000+ Unique K8s Deployments, How We Did It
35mOptimizing Kubernetes Deployments with Helm
55mHow to develop apps on K8s and not die trying
14mKeynote: Kubernetes is Still Hard (for Developers)
22mCreating a Micro Open-Source Community with Helm
40mHarnessing the Power of Open Source for Cloud Native Developm...
37mAutomated Provisioning using HELM charts on Kubernetes