Stop Writing Operators
Talkat KubeCon + CloudNativeCon North America 2020 Virtual · on Wednesday, 2020-11-18· at 15:00· Intrado Virtual Event Platform,·
summary
Argues Stop writing operators by default and shows concrete alternatives: use a Helm chart or GitOps, a simple CRD controller, an external manager, or a no‑code operator platform like KUDO or Operator Framework instead of an in-cluster operator. Recommends writing an operator only when you must manage someone else’s stateful app or need temporary backporting, and insists to measure recovery time before automating, keep loose coupling, write minimal code in a familiar language, and prefer moving logic into the app when possible.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:00Everybody's thinking it...
- 2:38Injunction vs. information
- 3:37Operators vs. controllers
- 5:54No state needs managing
- 6:45Apps you maintain
- 9:15CRD controller
- 11:56Run outside the cluster
- 13:07Case #1: Someone else's app
- 14:57Case #1: You don't have a map yet
- 17:14Case #2: 0.x app versions
- 18:10Did you talk to the owner?
- 20:15Choosing to use a framework ES Virtual
- 21:24When you write that operator
related talks
43mLessons learned writing 10+ Kubernetes Operators
29mRage Against the API-Machinery: Writing an Operator for Production
45mKubernetes Operators: Operating Cloud Native services at scale
36mEssential Patterns For Designing And Implementing Your Operator
17mAnti-patterns for Kubernetes Operators
39mKubernetes Operators: Managing Complex Software with Software
25mApp Operator: The Hidden Persona
28mSmooth Operator - A Rough Guide to Kubernetes Operators - Olive Power, VMware