App Operator: The Hidden Persona
summary
Argues for a distinct application operator role that sits above infrastructure ops and focuses on delivery, monitoring, safe deployment and securing app traffic; lists concrete tooling choices — Prometheus, Jenkins, Brigade, Datadog, Dynatrace, service mesh — and shows enterprises building UI layers (Rio, Knative, AKS) so developers never see Kubernetes. Warns CRDs fragment portability and proposes a common API layer above clusters so application behavior remains portable instead of tied to each vendor's extensions.
AI-written summary · about
chapters (10)
- 0:00Intro
- 4:22Operations on different environments is hard
- 6:47With K8's the operational role is becoming more "defined." • Kubernetes and the ecosystem only makes this job more important
- 8:23Kubernetes attempts to create a division between infra & applications
- 10:34The duties of the application operator
- 11:29App ops has many technologies at their
- 12:19App Ops must do a lot of plumbing to accomplish their tasks
- 13:04App Ops is forced to get into the weeds to accomplish their role
- 18:13Different Kubernetes "distros" popping up like weeds
- 20:05What if we could use a common API to avoid fragmentation?
related talks
25mApp Operator: The Hidden Persona
40mDevOps in the Cluster: A deep dive into operators
01h 33mBuilding for Global Engineering Platforms - Let's make an Operator
29mRage Against the API-Machinery: Writing an Operator for Production
42mKubernetes Operators: What are They and Why would You Need Them?
45mKubernetes Operators: Operating Cloud Native services at scale
35mPanel: State of the Operators: Hubs, Frameworks, SDKs, and Beyond
36mEssential Patterns For Designing And Implementing Your Operator