Kubernetes at the Home Office
summary
Home Office code moves as Docker images that include app code and deps, built by CI and Docker images pushed to Docker Hub, then deployed to Kubernetes where a pod + container model, Kubernetes replication controller set to replica=2, services provide DNS/load‑balancer IPs, secrets mount into pods and persistent volume claims attach storage. Deployments use rolling updates so two pods remain running during upgrades, health checks restart dead containers, and reuse plus open sourcing reduces repeated infra work.
AI-written summary · about
chapters (27)
- 0:00Start
- 4:14How do you run a container?
- 6:53Finding containers
- 8:23How do you make a
- 10:09What is docker?
- 15:17Continuous Integration
- 16:1112 Factor
- 18:02Docker is awesome but how to manage
- 19:04Solves
- 19:52Key Ideas
- 20:24Pods
- 21:34Replication Controller Running?
- 22:04Service
- 22:48Flappy Endpoint
- 26:12Can you keep a secret?
- 28:36Load Balancer
- 30:10Ship It
- 31:56Rolling Updates
- 37:23Solving the Management Puzzle
- 40:51Work like us
- 42:39Things We Reuse
- 43:00The worlds most successful code reuse project
- 45:10Being a good person (inside and out)
- 45:43Thinking like a Platform
- 47:33Thinking like a PaaS
- 49:17Work Securely
- 52:29Come be cool
related talks
01h 01mDeploying Kubernetes, a Container Cluster Manager
46mAround & After Kubernetes: The Principles and Ideas that Guide Us
39mUsing Kubernetes to Change Legacy Systems and Processes in the Public Sector
40mKubernetes - Easy Peasy
34mKubernetes at Home to Host Entertainment & Productivity Apps + More
29mA history of GOV.UK's infrastructure: the long voyage to Kubernetes
44mEvolving Dev and Ops with Kubernetes: Enterprise Adoption for Security, Speed, and Ease
19mLet's Deploy A Containerized Application