Run busybox pod as a privileged container#2
Merged
Conversation
This was referenced May 18, 2026
This was referenced May 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This demonstrates two ways to run busybox as a privileged container: a deployment and a daemonset.
The deployment is managed directly by the Operator. It creates a single pod/container and schedules it wherever.
The daemonset is just k8s yaml. I could do this in the Operator, but I haven't yet. Being a daemonset, it should be tied to an underlying workload node. It also mounts the workload node's
/path at/mnt/root. Combined with achroot, this lets us execute host vm commands. Not everything works, but this may be due to VM configuration. I can runps auxand see host VM processes though (ie containerd, kube*, etc).