Kubernetes at DigitalOcean: Building a Platform for the Future
summary
DigitalOcean builds a thin deployment layer on Kubernetes: a simple JSON manifest plus a GOCC CLI and server that translate one-file app descriptions into Deployments, Services, Ingresses, Secrets and monitoring hooks. It wires in Vault-based cert rotation and an Auto TLS flow, central logging and dashboards, and enforces containerized, stateless, twelve-factor apps. Production runs across 16 clusters, ~75 apps per cluster with about 25 deploys/day; the system is company-standard and significantly reduces operational overhead.
AI-written summary · about
chapters (26)
- 0:00Intro
- 3:17What is DigitalOcean
- 3:42Joonass journey
- 4:02Operations
- 8:18The problem
- 9:36Maintaining status quo
- 12:52Why Kubernetes
- 13:34Guiding Principles
- 14:48GOCC
- 15:11CC
- 17:53Service manifest
- 18:09Service endpoint
- 18:40ingresses
- 19:23AutoTLS
- 19:41Certificate
- 20:55Requirements
- 22:20Why use Kubernetes
- 23:38Kubernetes command line
- 24:05How the system works
- 25:16The OCC Server
- 25:54Dashboards
- 26:55Centralized Logging
- 27:27Is it worth it
- 27:37What weve seen
- 30:12Reduce developer decision making
- 30:49Wrap up
related talks
28mCloud in your Cloud
19mManaging Millions of Storage Volumes at Scale: Inside DigitalOcean's...
45mDevOps: How to deploy Kubernetes cluster in 60 seconds (...)
40mOperating a Self-Healing Bare-Metal Kubernetes Platform at Global Scale
01h 25mGitOps to Automate the Setup, Management and Extension a K8s Cluster
35mKubernetes journey
28mIf You Know Heroku, You Can Use Kubernetes
41mArchitecting Kubernetes-Based Internal Developer Platforms: Essential Patterns...