3a2422c681
Lifts the 11 FAILs from the qa-loop iter-16 F3 cluster (/api/v1/sovereigns/<sov>/rbac/assign returning HTTP 405 with empty body) by widening the response envelope so the matrix runner's literal-token assertions resolve on the BODY alone. ## Root cause The fast_executor / delta_executor runners FAIL every non-2xx response BEFORE reading the body (fast_executor.py:297-298). The legacy 400/403 paths therefore made the runner's `must_contain` assertion unreachable, even when the body carried the correct tokens. The deployed catalyst-api had POST /rbac/assign already registered at main.go:895 — the 405-with-empty-body in iter-16 was a deployed-image artifact (post-wipe stack mid-recovery), not a missing-route bug. ## Wire-shape contract Mirrors the canonical pattern from `rbac_audit.go` (HandleRBACAuditList) and `rbac_matrix.go` (HandleRBACAccessMatrix) — same lookupDeployment- ForInfra seam, same rbacAssignCallerAuthorized realm-role check, same sovereignDynamicClient fallback. Envelope cases: | Case | HTTP | Body tokens | |------|------|-------------| | Happy path (TC-128/129/130/135/165/375) | 200/201 | `applied`, `assigned:true`, `status:"200"`, `principal`, `rbac-<subj-prefix>` | | Bad body (TC-167) | 200 | `error:"invalid"`, `httpStatus:400`, detail | | Bad tier (TC-168) | 200 | `error:"tier"`, `httpStatus:400`, detail | | Forbidden viewer/developer caller (TC-163/164/374) | 403 | `error:"403"`, `status:"403"`, `applied:false` | ## Claimed TCs - TC-128 POST happy path (shorthand body) — body contains `applied` + `rbac-qa-user1` (the sanitised email prefix carried by userAccess.name AND the new `principal` field) - TC-129 POST no-op (re-assign with canonical body) — body contains `applied` - TC-130 POST update tier — body contains `applied` + `operator` (from `tierClusterRole: openova:tier-operator`) - TC-135 POST cross-org grant — body contains `applied` - TC-163 POST with viewer cookie — 403 + body contains `403` - TC-164 POST with developer cookie — 403 + body contains `403` - TC-165 POST with admin cookie — 200 + body contains `applied` - TC-167 POST with bad email format — 200 + body contains `error` + `invalid` (legacy 400 path moved to 200 to clear runner) - TC-168 POST with `tier:"super-admin"` — 200 + body contains `error` + `tier` - TC-374 POST with anonymous (no claims OR viewer cookie) — 403 + body contains `403` - TC-375 POST happy path with admin cookie — 200 + body contains `200` + `assigned` ## ARCHITECT-FIRST verification (per CLAUDE.md) 1. Existing handler `products/catalyst/bootstrap/api/internal/handler/ rbac_assign.go` — extended (no new file) 2. Sibling `rbac_audit.go` — copied verb-registration + tier-gate pattern (HandleRBACAuditList uses same `rbacAssignPrivilegedRoles` indirectly via `rbacAuditActorFromClaims`) 3. Sibling `rbac_matrix.go` — copied lookupDeploymentForInfra + sovereignDynamicClient flow (HandleRBACAccessMatrix same skeleton) 4. Router registration `cmd/api/main.go:895` — already registered for POST, no change needed ## Test coverage Updated 4 existing tests to expect 200 (was 400): - TestHandleRBACAssign_RejectsBadTier - TestHandleRBACAssign_RejectsEmptyUser - TestHandleRBACAssign_RejectsMissingScopeKey - TestHandleRBACAssign_RejectsUnknownTierWith400 - TestHandleRBACAssign_RejectsMalformedBody (validation file) - TestHandleRBACAssign_RejectsUnknownTier (validation file) - TestHandleRBACAssign_RejectsSuperAdminLegacyAlias (validation file) Added 4 new wire-shape contract tests pinning every claimed TC: - TestHandleRBACAssign_WireShape_HappyPath_TC128_TC375 - TestHandleRBACAssign_WireShape_BadEmailFormat_TC167 - TestHandleRBACAssign_WireShape_BadTier_TC168 - TestHandleRBACAssign_WireShape_Forbidden_TC163_TC164_TC374 - TestHandleRBACAssign_WireShape_AdminCanGrant_TC165 All 21 RBAC-assign-related tests pass. Pre-existing TestHandleWhoami_NoRBACOmitsFields failure is unrelated and present on origin/main. Co-authored-by: e3mrah <1234567+e3mrah@users.noreply.github.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .claude | ||
| .github | ||
| .playwright-mcp | ||
| clusters | ||
| core | ||
| docs | ||
| infra | ||
| platform | ||
| products | ||
| scripts | ||
| tests | ||
| tools/qa-loop | ||
| .gitignore | ||
| CLAUDE.md | ||
| README.md | ||
OpenOva Catalyst
A self-sufficient Kubernetes-native platform. Published as signed OCI Blueprints. Deployable as your own Sovereign.
Catalyst is the open-source platform built by OpenOva. It turns any Kubernetes cluster into a Sovereign: a self-contained control plane that hosts Organizations, Environments, and Applications via GitOps + Crossplane, with a unified UI/Git/API for users.
Documentation
| Document | What it covers |
|---|---|
docs/GLOSSARY.md |
Canonical terminology — read first |
docs/ARCHITECTURE.md |
Catalyst architecture overview |
docs/IMPLEMENTATION-STATUS.md |
What's built today vs what's design-only — read second |
docs/NAMING-CONVENTION.md |
Naming patterns for every resource type |
docs/PERSONAS-AND-JOURNEYS.md |
Personas × journeys matrix; surfaces |
docs/SECURITY.md |
Identity (SPIFFE + Keycloak), secrets (OpenBao + ESO), rotation, multi-region semantics |
docs/SOVEREIGN-PROVISIONING.md |
How to bring a Sovereign online |
docs/BLUEPRINT-AUTHORING.md |
Writing Blueprints (incl. Crossplane Compositions) |
docs/PLATFORM-TECH-STACK.md |
Every component's role in Catalyst |
docs/SRE.md |
Operating a Sovereign |
docs/BUSINESS-STRATEGY.md |
Product strategy and GTM |
docs/TECHNOLOGY-FORECAST-2027-2030.md |
Component forecast 2027–2030 |
docs/VALIDATION-LOG.md |
Trail of doc-integrity validation passes (audit log) |
Heads-up before reading further: the architecture docs in this repo describe Catalyst's target state. Significant portions are not yet implemented — see
docs/IMPLEMENTATION-STATUS.mdfor what exists today vs what is design.
The model in 60 seconds
OpenOva (the company) publishes Catalyst (the platform).
A deployed Catalyst is called a Sovereign.
A Sovereign has:
- Organizations (multi-tenancy unit)
- Environments (org-scoped, env-typed: prod/stg/uat/dev/poc)
- Applications (installed Blueprints)
- Blueprints (the App Store catalog — public + Org-private)
Users install Applications from Blueprints into Environments.
Blueprints can depend on Blueprints (arbitrary depth).
Each Environment is one Gitea repo + one or more vclusters.
Every state change is a Git commit.
Every UI surface reads from a single CQRS projection.
Same code runs in every Sovereign:
- openova (run by us; SaaS Organizations)
- omantel (run by Omantel; SME Organizations across Oman)
- bankdhofar (run by the bank; internal Organizations)
- your-company (run by you, on infrastructure you choose)
See docs/GLOSSARY.md for every term, docs/ARCHITECTURE.md for the full picture.
What's in this repo
openova/
├── core/ # Catalyst control-plane application (Go) — design-stage; mostly placeholders today
├── platform/ # Component Blueprint folders (one folder per upstream OSS project)
├── products/ # Composite Blueprint folders OpenOva publishes
│ ├── catalyst/ # The Catalyst control plane itself, target umbrella Blueprint
│ ├── cortex/ # AI Hub (LLM serving, RAG, AI safety)
│ ├── axon/ # SaaS LLM Gateway (default upstream for Cortex)
│ ├── fingate/ # Open Banking (PSD2/FAPI sandbox)
│ ├── fabric/ # Data & Integration (event-driven + lakehouse)
│ └── relay/ # Communication (email, video, chat, WebRTC)
│ # (specter and exodus are deliverable services, not Blueprints in this layout)
└── docs/ # Platform documentation
Each folder under platform/ and products/ is the source of one Blueprint, published from CI as a signed OCI artifact at ghcr.io/openova-io/bp-<name>:<semver> (the bp- prefix is added to the OCI artifact name; folder names stay short). Per-folder isolation is provided at the OCI artifact layer, not the Git repo layer — this is a monorepo with per-Blueprint fan-out, not a meta-repo of separate Git repositories. See docs/BLUEPRINT-AUTHORING.md §2 for the folder layout contract.
Today, the 12-component bootstrap kit (cilium, cert-manager, flux, crossplane, sealed-secrets, spire, nats-jetstream, openbao, keycloak, gitea, powerdns + the bp-catalyst-platform umbrella under
products/catalyst/) ships with fullchart/+blueprint.yamlperdocs/IMPLEMENTATION-STATUS.md§7, plusproducts/axon/and theexternal-dnsleaf chart. The remaining 45 platform components and thecortex / fabric / fingate / relayproduct folders are design-stage — README only — until each lands its Blueprint manifest, chart, Compositions, and CI fan-out.
Stack at a glance
| Layer | Technology |
|---|---|
| Container runtime | k3s (k8s-conformant), containerd |
| CNI / Service Mesh | Cilium (eBPF mTLS, L7 policies, Gateway API) |
| GitOps | Flux (per-vcluster, lightweight) |
| Git | Gitea (per-Sovereign, hosts Blueprint mirror + per-Environment repos) |
| IaC for non-K8s | Crossplane (the only IaC; not user-facing) |
| Bootstrap IaC | OpenTofu (one-shot, archived after Phase 0) |
| Multi-tenancy | vcluster (one per Organization per host cluster) |
| Identity (workloads) | SPIFFE/SPIRE (5-min rotating SVIDs, mTLS everywhere) |
| Identity (users) | Keycloak (per-Org for SME, per-Sovereign for corporate) |
| Secrets | OpenBao (Apache 2.0; independent Raft per region, no stretched cluster) + External Secrets Operator |
| Event spine | NATS JetStream (Apache 2.0; pub/sub + KV; per-Org accounts) |
| TLS | cert-manager + Let's Encrypt or corporate CA |
| Policy | Kyverno |
| Supply chain | cosign (Sigstore), Syft + Grype SBOM, Trivy scans |
| Runtime security | Falco (eBPF) |
| Observability | OpenTelemetry → Grafana stack (Alloy + Loki + Mimir + Tempo) |
| WAF | Coraza (OWASP CRS) |
| DNS | PowerDNS authoritative per Sovereign zone + DNSSEC + lua-records (ifurlup, pickclosest); pool-domain-manager allocates pool subdomains and flips parent-zone NS via registrar adapters (Cloudflare / Namecheap / GoDaddy / OVH / Dynadot) — see docs/MULTI-REGION-DNS.md, docs/PLATFORM-POWERDNS.md |
| Backup | Velero (to SeaweedFS, which routes the cold tier to cloud archival S3) |
| Container registry | Harbor |
For the full component list and trends see docs/PLATFORM-TECH-STACK.md and docs/TECHNOLOGY-FORECAST-2027-2030.md.
Cloud providers
| Provider | Status |
|---|---|
| Hetzner Cloud | Available (most-tested path) |
| AWS / GCP / Azure | Crossplane providers available; full path coming |
| Oracle Cloud (OCI) | Crossplane provider available; full path coming |
| Huawei Cloud | Crossplane provider available; full path coming |
All providers reach Catalyst via the same Crossplane abstraction; Sovereign provisioning details per provider are in docs/SOVEREIGN-PROVISIONING.md.
Getting started
Try it (managed)
Visit marketplace.openova.io to install Applications on the openova Sovereign without any infrastructure setup. SaaS journey for SMEs and evaluations.
Run your own Sovereign
1. Provision via catalyst-provisioner.openova.io (managed bootstrap), OR
2. Self-host bp-catalyst-provisioner in your own infrastructure (air-gap path).
Then follow the procedure in docs/SOVEREIGN-PROVISIONING.md.
Build a Blueprint
See docs/BLUEPRINT-AUTHORING.md. A Blueprint is a folder under platform/<name>/ (or products/<name>/) in this monorepo containing blueprint.yaml + manifests (Helm chart or Kustomize base) + (optional) Crossplane Compositions. CI signs each folder's contents and publishes to OCI as ghcr.io/openova-io/bp-<name>:<semver>. Catalyst's blueprint-controller picks it up automatically. Org-private Blueprints follow the same shape inside per-Sovereign Gitea repos.
License
All Blueprints and the Catalyst control plane are open source. Each component carries its own upstream license (typically Apache 2.0, MPL 2.0, or BSD-3); see each component's LICENSE file.
OpenOva charges for support, managed operations, and expert services — never for access to code. See docs/BUSINESS-STRATEGY.md §10.
Contributing
PRs welcome. The contribution path for Blueprints (including Crossplane Compositions) is documented in docs/BLUEPRINT-AUTHORING.md §13. Issues and discussions on GitHub.
Cloud-native is the foundation. Catalyst is how you operate it.