Deep dive into container orchestrator options on Azure
summary
Concrete choices and outcomes: run Docker on a VM with the Docker extension, use solution templates or let Azure Container Service provision DC/OS Kubernetes or Swarm (preconfigured ARM templates), or adopt platform options like Service Fabric, Web Apps or Batch. ACS exposes a CLI, an SLA and a private Azure Container Registry, and the generation tooling is open source as the ACS engine on GitHub. The talk cites 38 datacenter regions and that ~60% of deployments use Kubernetes Swarm or Mesos and shows small demos (clusters with one master and two agents running three nginx replicas).
AI-written summary · about
chapters (11)
- 0:00Container orchestration on Azure
- 1:25Containers on Azure VMs
- 6:29Orchestrator solution templates
- 10:38Azure Container Service
- 15:56Customizing ACS Engine
- 17:23Demo: ACS CLI tools
- 24:25CI/CD with ACS
- 25:51Azure Service Fabric
- 29:08OpenShift and Cloud Foundry on Azure
- 29:48Serverless containers on Azure
- 31:17Summary
related talks
01h 09mRunning containerized applications on Azure Container Services
01h 07mDocker Containers on Azure - let me count the ways
49mAZURE CONTAINERS AND KUBERNETES PLATFORM
37mContainer Service: Not Only
01h 00mPractical Container Scenarios in Azure
30mCloud, Containers, Kubernetes
01h 06mSo many Docker platforms, so little time...
19mSessie 3 Docker
