K-C4 · size M · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
Pod Security restricted everywhere, drop ALL, read-only root, seccomp RuntimeDefault, no service-account tokens, default-deny NetworkPolicies with the allow list from the plan, secrets only from existingSecret mounted as files.
Done when
Lab namespace enforces restricted and passes
NetworkPolicy map documented
Depends on: S2, K-S2
**K-C4** · size M · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
Pod Security restricted everywhere, drop ALL, read-only root, seccomp RuntimeDefault, no service-account tokens, default-deny NetworkPolicies with the allow list from the plan, secrets only from existingSecret mounted as files.
**Done when**
- Lab namespace enforces restricted and passes
- NetworkPolicy map documented
**Depends on:** S2, K-S2
jcoffey-dev
added this to the 27.1 milestone 2026-11-18 05:14:43 +00:00
NetworkPolicies are on by default: every pod starts from deny-all. The map is in the README under "Security defaults".
The lab's inbuxa namespace enforces Pod Security restricted. Every pod was re-admitted under it, the upgrade Job ran, and the sign-in and mail tests pass. On kind, the blocked paths were probed and are blocked.
One secret is still an environment variable until #19 merges with server rc.32: the webmail's client secret, on the server's side.
Done in #21 and inbuxa/inbuxa-k8s-lab#21.
- NetworkPolicies are on by default: every pod starts from deny-all. The map is in the README under "Security defaults".
- The lab's `inbuxa` namespace enforces Pod Security restricted. Every pod was re-admitted under it, the upgrade Job ran, and the sign-in and mail tests pass. On kind, the blocked paths were probed and are blocked.
One secret is still an environment variable until #19 merges with server rc.32: the webmail's client secret, on the server's side.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
K-C4 · size M · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
Pod Security restricted everywhere, drop ALL, read-only root, seccomp RuntimeDefault, no service-account tokens, default-deny NetworkPolicies with the allow list from the plan, secrets only from existingSecret mounted as files.
Done when
Depends on: S2, K-S2
Folded into the checklist on inbuxa/inbuxa-charts#14 to keep the issue list short. The details stay here; reopen this when work on it starts.
Done in #21 and inbuxa/inbuxa-k8s-lab#21.
inbuxanamespace enforces Pod Security restricted. Every pod was re-admitted under it, the upgrade Job ran, and the sign-in and mail tests pass. On kind, the blocked paths were probed and are blocked.One secret is still an environment variable until #19 merges with server rc.32: the webmail's client secret, on the server's side.