DIY Mesos Executor
summary
Custom Mesos executors replace the default to do three concrete things: injects TLS certs and encrypted config into task env (a CA signs agent certs, executor fetches encrypted config and fills env vars), registers instances in Consul and removes them before SIGTERM to enable true graceful shutdown, and streams logs from task stdout for centralized rotation. The talk cites switching to executors and reduced deployment errors from thousands to ~200 by eliminating Mesos event delays; HTTP v1 API is recommended for new executors.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:01Recap
- 2:04Types of Executors
- 3:11Cloud Native 12 Factors
- 7:20Conflicts
- 10:03Possibilities
- 14:15Task lifecycle
- 18:01Default Executors
- 20:04Graceful Shutdown
- 21:51Locks
- 23:10Metadata
- 24:00Container logger
- 25:03Custom executors
- 25:45Aurora
- 26:26Singularity
- 26:59Other Companies
- 27:39Summary
related talks
38mBootstrapping Secure Mesos Clusters
45mMulti-Runtime Service Mesh With Consul
29mHow Security Requirements Turned Us into Accidental Chaos Engineers
36mSeccomp For Developers - Writing More Secure Applications
18mA Secure Tekton Task by Using Confidential Containers
25mAdministering Multi Cluster Service Meshes Securely
15mLightning Talk: Automate and Secure Consul Service Mesh on AWS ECS
42mTaking Eclipse Che to the enterprise