Worker capability and seccomp settings are not configurable through WorkerPool #2422

The WorkerPool API in v0.4.0 exposes placement, resources and ServiceAccount selection, but not the worker container’s Linux capabilities or seccomp profile.

The controller generates gVisor workers with:

• UID/GID 0.
• privileged: false.
• All capabilities dropped, followed by an explicit set of 13.
• seccompProfile: Unconfined.
• appArmorProfile: Unconfined.

These settings are defined in the controller. Editing the generated Deployment is not persistent because the controller reconciles it. A Helm post-renderer does not change worker Deployments created later by the controller.

Applying different capability restrictions or a seccomp profile therefore requires configuration outside WorkerPool.

Versions

Reproduced with:

• Agent Substrate v0.4.0, commit 756c2a53741121e728f4cc3066c8a19e575b4919.
• Kubernetes v1.35.0 on kind.
• containerd 2.2.0.
• Linux 7.0.14, arm64.
• gVisor nightly 2026-09-02, systrap.

References

• WorkerPool template fields
• Generated worker security context

Related: #2084 concerns WorkerPool authorisation and privilege boundaries; #1368 concerns startup under the runtime-default seccomp profile. This report concerns configuration of the host-facing worker, not capabilities granted inside an actor.