BOSH Working Hand-in-Hand with SystemD, a Story About Authoring a BOSH Release
summary
Builds a modern BOSH release to run Kubernetes on ContainerD by bridging BOSH BPM with systemd cgroup ownership: BPM launches a lightweight postprocess that starts a systemd unit with Delegate=yes, a fail-wrapper forces unit failure and uses OnFailure to trigger a templated notify unit that grabs the postprocess PID and sends SIGINT, letting monit restart things. Tools are BOSH BPM, systemd units, a postprocess shim and fail-wrapper; prototype works and will be open sourced.
AI-written summary · about
chapters (12)
- 0:00Introduction and motivation
- 1:09BOSH and Kubernetes overview
- 2:12Why BOSH for Kubernetes
- 3:37Previous BOSH Kubernetes releases
- 4:18Upgrading the Kate’s BOSH release
- 6:05Problem with containerD and systemd
- 7:12BPM and systemd cgroups conflict
- 8:18Garden’s BPM mode limitations
- 8:39Designing a new solution
- 12:53Final solution and workflow
- 13:35Future of BOSH and systemd
- 14:19Open source plans and conclusion
related talks
13mAuthoring a BOSH Release Is Actually Easy!
06mYou mean I don't have to write a BOSH release?
08mYou CAN Teach an Old BOSH New Tricks!
39mManaged CF-as-a-Service: An Operator's Cookbook
30mOn-Demand Data Services with Cloud Foundry - Maria Ntalla & Simon Jones, Pivotal
01h 12mPKS: The What and How of Enterprise-Grade Kubernetes
36mKubo - Your Gateway Drug to Cloud-Native - Cornelia Davis, Pivotal
37mBuilding a Managed Platform While Maintaining a Good Developer Experience