Public: anyone can read this; nobody can change it.

workbenchthis machine

/goal /ultracode-workflows [DOM-2] swap CNI to Cilium + replace blanket app egress with domain/identity-defined CiliumNetworkPolicy (closes #13) #37

Closed opened this view on origin

Closed without the crew

opened this view on origin

Track/Wave: DOM-2 · Wave G5 · Size XL Repos: mitosis, gitops, mcp, _app-template Depends on: DOM-1a, HYB-1, RBAC-4

Why

Realizes 'the network is domain-defined': per-app FQDN egress instead of the interim blanket 443/80 allow. User chose to build now. Closes #13.

Scope

(a) CNI swap at bring-up — bin/up's k3d create installs Cilium (flannel-backend=none + Cilium Helm); VERIFY every existing networking.k8s.io/v1 NetworkPolicy still enforces natively before adding Cilium rules. (b) A per-app allowedHosts spec (charts/app values) that the overlay renderer turns into a CiliumNetworkPolicy toFQDNs rule, REPLACING the blanket allow as the default, keeping RFC1918-exclusion + intra-ns/Traefik/CoreDNS rules.

Acceptance

A fresh bin/up cluster runs Cilium (cilium status Ready); all existing platform NetworkPolicies still enforce; an app declaring allowedHosts:[api.example.com] blocks a non-allowlisted host and allows the allowlisted one; a no-allowedHosts app is rejected/defaulted per policy.

Notes

Seam A (bin/up) AFTER HYB-1 + Seam B (overlay) AFTER RBAC-4 — last on both. MIGRATION RISK: adopting Cilium on the already-live client platform is a CNI migration; validate on staging, then plan deliberate migration or re-germinate. HAZARD: must preserve cert-manager ACME DNS-01 egress (shared with POL-4).

--- Part of the First Client Deploy → Governance roadmap. The owning agent may recurse into its own subagent team (ultracode workflow) if the task warrants. Honor the seam-serialization: land on a shared seam by rebase, and don't start a seam position until the prior one has merged.

commented

DOM-2 delivered as a SPLIT: the per-app FQDN-egress renderer is MERGED (mcp#10 + _app-template#5, default-off PLAT_FQDN_EGRESS, proven live on Cilium — allow/block correct, std netpols still enforce). The Cilium CNI SWAP is a documented NO-GO on current k3s/k3d (registry hostPort + kpr apiserver-cert blockers) — kept kube-router, prerequisite tracked in a new issue. The domain-defined-network capability is ready and lights up the moment the platform runs on Cilium.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs