platform/orca-platform

Fork 0

Files

T

History

sharang 6be727d404

ci / shared (push) Successful in 9s

Details

ci / validate (push) Successful in 4s

Details

refactor(iac): cluster split — 1 cluster per plane, breakpilot-* naming (#6 )

3 Orca clusters (breakpilot-edge / breakpilot-control / breakpilot-app), 1 plane each. Single-VM core with Keycloak co-tenant on vm-edge. App cluster gets prod + stage VMs. Manifests reorganized into clusters/<name>/services/; validator now enforces per-cluster node whitelist. Multi-VM rollout gated on legal entity.

2026-06-30 20:30:14 +00:00

dev

feat(iac): scaffold orca-platform layout (M1.1)

2026-05-18 20:28:40 +00:00

prod

refactor(iac): cluster split — 1 cluster per plane, breakpilot-* naming (#6 )

2026-06-30 20:30:14 +00:00

stage

refactor(iac): cluster split — 1 cluster per plane, breakpilot-* naming (#6 )

2026-06-30 20:30:14 +00:00

README.md

feat(iac): scaffold orca-platform layout (M1.1)

2026-05-18 20:28:40 +00:00

README.md

Overlays

Per-env sparse deltas applied on top of manifests/. Concept: each overlay file may set just the fields that differ from the base manifest. The merge script in scripts/plan.sh produces the final per-env service set at .orca-out/<env>/.

For now the overlays are placeholder structures — concrete deltas land with the milestones that introduce real images and replica counts (M4.1, M5.1, M6.x).