Skip to content

Add runtimeClassName, automountServiceAccountToken and egress rules - #11

Merged
Temikus merged 2 commits into
mainfrom
feat/pod-sandbox
Nov 11, 2026
Merged

Temikus merged 2 commits into
mainfrom
feat/pod-sandbox

Conversation

@Temikus

@Temikus Temikus commented Nov 11, 2026

Copy link
Copy Markdown
Owner

Purpose

Lets a workload run sandboxed: under a RuntimeClass such as gVisor, without an API token, and with egress limited to listed rules. Needed to isolate an agent workload that runs untrusted code.

What a reviewer needs to know

  • runtimeClassName and automountServiceAccountToken: rendered on the pod spec only when set. false is honoured; null (default) omits the field.
  • networkPolicy.egress: non-empty adds Egress to policyTypes and renders the rules as-is. Empty keeps today's ingress-only policy.
  • No change for existing users: all defaults render as before, and snapshots don't move.
  • Release: the second commit bumps to 1.11.0; tag v1.11.0 after merge.
Verification
  • helm unittest: 209 pass. The two new behaviour tests fail against the old templates.
  • ci/statefulset-values.yaml now sets all three, so kubeconform validates the rendered pod and policy.
  • helm lint passes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01YGMCH6ZYgjPPWruHDyt2HP

Lets a workload run sandboxed: under a RuntimeClass such as gVisor,
without an API token, and with egress limited to the listed rules.
All three default to today's output, so existing snapshots don't move.

Claude-Session: https://claude.ai/code/session_01YGMCH6ZYgjPPWruHDyt2HP
@Temikus
Temikus merged commit f308eb3 into main Nov 11, 2026
3 checks passed
@Temikus
Temikus deleted the feat/pod-sandbox branch November 11, 2026 08:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant