Keynote: Are We There Yet?
summary
Argues there is no clear winner in container orchestration, shows Azure Container Service deliberately supports Kubernetes, DC/OS and Mesos, and shares paid-customer usage patterns that vary by workload. Demonstrates a real Helm workflow: helm install deploys a Kubernetes microservice that pulls connection info from a service broker and binds to a provisioned DC/OS Cassandra instance on Azure, with the DC/OS cluster created live from GitHub-backed, early-stage code.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:04Gartner hype cycle
- 3:34Orchestration survey data
- 6:22Experimental code and collaboration
- 8:50Windows Server containers
- 11:42Demo and Kubernetes
- 14:10Deploying with Kubernetes
- 20:41Future collaboration
related talks
49mAZURE CONTAINERS AND KUBERNETES PLATFORM
14mKeynote: Kubernetes is Still Hard (for Developers)
07mKeynote: Container-Native Dev-and-ops Experience: It's Getting Easier, Fast.
20mKeynote: Kubernetes: This Job is Too Hard: Building New Tools, Patterns and Paradigms to Democratize
37mContainer Service: Not Only
30mCloud, Containers, Kubernetes
01h 01mCloud, Containers, Kubernetes
15mKeynote: Kubernetes