Ignites- Containers, Virtual Machines...
summary
Claim: pick infrastructure by state and isolation not hype. Containers run stateless → containers like web servers or ephemeral caches and remain portable because persistent data stays off image. Production databases go on stateful databases → VMs so you can back up and patch. Heavy, noisy workloads run on heavy compute → bare metal to avoid noisy neighbors. Kubernetes offers Kubernetes StatefulSets mount persistent volumes which keep data out of containers while automating attachment.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:29Is Bare Metal Dead
- 0:44Why do people still use bare metal
- 0:59Is virtual machine infrastructure dead
- 1:14Does everyone run everything in containers
- 1:29Containers are not for everything
- 1:44Containers are not for production databases
- 1:59Stateful
- 2:15Persistent Data
- 2:30Locked Host
- 2:45Container vs Virtual Machine
- 3:01Containers
- 3:31Kubernetes
- 3:46Stateful Sets
- 4:01The Ten Commandments of Infrastructure
- 4:16Stateless Parts
- 4:31Persistent Data Stores
- 4:46Heavy Compute Load
related talks
38mThe Container Operator’s Manual
37mBuilding Stateful Workloads in Kubernetes
44mContain yourselves
21mHybrid Cloud - nothing to worry about! 🌥️
46mDeploying and maintaining software for today's infrastructure
49mKeep you data safe in a containerized application
26mNavigating the Wild West of Building and Deploying Container
05mIgnite: The History of Linux Containers