Pod shape: namespace, pool, sandbox, egress #4

New issue

Closed

opened 2026-10-31 13:09:03 +00:00 by mikluko · 1 comment

mikluko commented

2026-10-31 13:09:03 +00:00

Owner

Map: #1

Question

What is the pod's shape: namespace, ServiceAccount name, Karpenter pool (arm64), resources, non-root and read-only root filesystem, CiliumNetworkPolicy egress allowlist, and whether Claude Code runs with --dangerously-skip-permissions there? The answer is what the manifests and the OpenBao role are written from.

Map: #1 ## Question What is the pod's shape: namespace, ServiceAccount name, Karpenter pool (arm64), resources, non-root and read-only root filesystem, CiliumNetworkPolicy egress allowlist, and whether Claude Code runs with `--dangerously-skip-permissions` there? The answer is what the manifests and the OpenBao role are written from.

mikluko added the

wayfinder:grilling

label

2026-10-31 13:09:15 +00:00

mikluko added a new dependency

2026-10-31 13:09:17 +00:00

#6 OpenBao: identity agent-rex

mikluko added a new dependency

2026-10-31 13:09:18 +00:00

#8 Deploy kuberex on saraksh via Flux HelmRelease

mikluko self-assigned this

2026-10-31 13:11:20 +00:00

mikluko commented

2026-10-31 14:28:42 +00:00

Author

Owner

Answer

Namespace agents, ServiceAccount rex.
Pinned to bulgakov (amd64 bare metal, workstation role): nodeSelector kubernetes.io/hostname: bulgakov, tolerations for sarak.sh/baremetal and sarak.sh/workstation.
Resources: requests 1 CPU / 2Gi, limits 4 CPU / 8Gi.
Storage: no PVC; hostPath /srv/rex on bulgakov mounted at /var/lib/rex.
Sandbox: non-root (rex), read-only root filesystem with writable /var/lib/rex, /run/rex, /tmp; all capabilities dropped, allowPrivilegeEscalation: false, seccomp RuntimeDefault.
Egress: open internet; in-cluster destinations denied except DNS and kube-apiserver.
Claude Code in Rex terminals defaults to --dangerously-skip-permissions; the pod is the sandbox.
Consequence: the image becomes multi-arch (amd64 + arm64), so it runs on bulgakov and still boots Apple container machines.

## Answer - Namespace `agents`, ServiceAccount `rex`. - Pinned to `bulgakov` (amd64 bare metal, workstation role): nodeSelector `kubernetes.io/hostname: bulgakov`, tolerations for `sarak.sh/baremetal` and `sarak.sh/workstation`. - Resources: requests 1 CPU / 2Gi, limits 4 CPU / 8Gi. - Storage: no PVC; hostPath `/srv/rex` on `bulgakov` mounted at `/var/lib/rex`. - Sandbox: non-root (`rex`), read-only root filesystem with writable `/var/lib/rex`, `/run/rex`, `/tmp`; all capabilities dropped, `allowPrivilegeEscalation: false`, seccomp `RuntimeDefault`. - Egress: open internet; in-cluster destinations denied except DNS and kube-apiserver. - Claude Code in Rex terminals defaults to `--dangerously-skip-permissions`; the pod is the sandbox. - Consequence: the image becomes multi-arch (amd64 + arm64), so it runs on `bulgakov` and still boots Apple `container` machines.

mikluko closed this issue

2026-10-31 14:28:42 +00:00

mikluko referenced this issue

2026-10-31 14:28:43 +00:00

Map: Rex server on saraksh #1

mikluko referenced this issue

2026-10-31 15:49:30 +00:00

Image toolchain for agents in Rex terminals #5