App Operator: The Hidden Persona
summary
Argues that enterprises need a dedicated application operator distinct from infrastructure admins and developers, responsible for CI/CD, monitoring, safe upgrades and traffic security rather than cluster plumbing; cites tooling choices like Prometheus, Grafana, Datadog, deployment patterns via service meshes and Istio for canaries, and limits of Helm for lifecycle management; notes managed Kubernetes (AKS) still forces infra work, and points to Rio and Knative and customer-built UIs as emerging solutions.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:50Operators manage everything from infrastructure to apps
- 4:22Operations on different environments is hard
- 5:05Kubernetes created a common control plan
- 6:47With K8's the operational role is becoming more "defined."
- 8:23Kubernetes attempts to create a division between infra & applications
- 8:39K8s makes things easier but complex at the same time
- 9:27There is room for a new role in the eco-system.
- 10:34The duties of the application operator
- 11:29App ops has many technologies at their disposal to accomplish their tasks
- 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
39mKubernetes Operators: Managing Complex Software with Software
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
29mRage Against the API-Machinery: Writing an Operator for Production
01h 33mBuilding for Global Engineering Platforms - Let's make an Operator