Declarative & Imperative Kubernetes Operations with Temporal & M3
Talkat KubeCon + CloudNativeCon North America 2021 · on Friday, 2021-10-15· at 15:25· Room 403 AB + Online·
summary
Operators manage desired state but struggle with multi-step imperative actions, so Temporal + the M3DB Operator coordinate safe cluster upgrades. Temporal guarantees workflows resume after crashes and runs nested/parallel workflows that check cluster health, enforce quorum across three replicas, and prompt via Slack-driven approvals. The operator uses an annotate statefulsets to hand off control pattern and an on-delete update strategy to delete pods in controlled batches; rollbacks are just new workflows.
AI-written summary · about
chapters (12)
- 0:00What is Kubernetes
- 7:23Workflows
- 10:52Temporal
- 12:14Safety
- 13:23Chronosphere
- 14:19Deployer
- 15:25Stateful Updates
- 16:14Deployment Workflow
- 17:00Workflow Overview
- 17:54Health Checks
- 18:46Slack
- 19:36Summary
related talks
35mBuild fault tolerant, distributed apps with Kubernetes and Temporal
26mRethinking Cloud-Native Patterns on Kubernetes
26mOperating Cassandra in Kubernetes with Temporal
53mAutomating Stateful Applications with Kubernetes Operators
31mTemporal: React for the Backend
34mEvolution of deployment tooling @ Chronosphere
36mKubernetes Day 2: Cluster Operations [I]
24mAutomating Stateful Apps with Kubernetes Operators