Improve docs about the 'bpm.enabled' property #359
+15
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi there,
After having worked extensively on running ContainerD with BPM in yet another Kubernetes BOSH Release (which is still private though), I wanted to update the docs here about the consequences of enabling BPM, now that Garden (using ContainerD by default) relies on being run by systemd for the sake of its cgroups being preserved.
And to bring a bit more context in: as mentioned in my recent talk (in May) https://youtu.be/pVxKltt4egI?t=495s in 2024 release authors must use BPM. That's also related to the preparation work in Noble stemcells for an alternative to using Monit (tracked in cloudfoundry/community#892). That's why I've worked so hard recently at solving the challenge of running ContainerD using BPM. I'll submit a talk and publish my work soon.
Don't hesitate to raise any concerns, mention necessary additions or correct anything that wouldn't be accurate.
Best,
Benjamin