Best way to persist a systemd and kubelet config flag change, without rolling my own version #3889
Unanswered
james-masson
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm looking at adding support for CPU partitioning into a Bottlerocket installation.
For this, I need to:
--system-reserved-cgroup=system
Arguably, the second parameter should be the default in Bottlerocket anyway...
How best to accomplish this, with a lot of Rust coding and rolling my own version?
The config must survive a reboot, because only on a fresh boot with this configuration are these parameters effective. I already use
reboot-to-reconcile
for other kernel flags.I anticipated having a bootstrap/superpowered container to make the change, but it doesn't solve the persistence issues.
Beta Was this translation helpful? Give feedback.
All reactions