All you need to know to get started with microservices on Kubernetes
summary
A runnable demo called twistcore implements four microservices (front, admin, scoring, persist) packaged as Docker images pushed to gcr io then deployed to a JKE Kubernetes cluster with three nodes; front runs three replicas while persist and scoring run one and two respectively. Resources are YAMLs applied with kubectl apply, configuration uses configMap and Secret mounted into pods, service discovery relies on ClusterIP services and an ingress with external IP. Rolling updates, port‑forward tests and logs confirm deployment and load balancing work end to end, and Google claims four billion containers per week.
AI-written summary · about
chapters (26)
- 0:00Intro
- 0:27Alain Regnier
- 2:59Docker
- 3:47Why use containers?
- 5:23Google and containers
- 6:42Kubernetes Details
- 7:30Monolithic Application
- 10:30Kubernetes Resource : Deployment
- 11:48Kubernetes Resource : Service
- 14:57Kubernetes Resource : Ingress
- 17:48Kubernetes Resource : Secret and ConfigMap
- 20:12Scenario : twiscore
- 25:14Project creation
- 25:34Database / Cloud Shell
- 26:05twiscore-persist.py
- 27:37Web Preview
- 29:42Container test
- 30:24Container push
- 31:23Kubernetes cluster
- 31:46Kubernetes Secret
- 32:10Kubernetes Config Map
- 36:42Kubernetes Deployment test
- 39:17Code update
- 41:13Kubernetes Ingress test
- 43:19Microservices and Kubernetes
- 44:26Services Mesh and Istio
related talks
49mDeveloping microservices applications on the Kubernetes platform
56mResilient Java based microservices with Kubernetes
46mModern DevOps with Kubernetes
36mMicroservices in the Cloud with Kubernetes and Istio
54mJava based microservices, containers, Kubernetes - how to
53mNext Generation Microservices
01h 04mNavigating microservices with .NET Core
37mManaging Containers at Scale with CoreOS and Kubernetes