Self-hosted clone of https://github.com/openova-io/openova (post-cutover, standalone)

Go to file

e3mrah 15ae8796bc fix(sovereign-console): close DoD gaps — Invariant + missing endpoints + chroot fetchers (#1044 ) This is the comprehensive fix for the chroot Sovereign Console DoD gaps caught on omantel.biz 2026-05-06. Eight pages were broken with "Something went wrong!" / "Invariant failed" / "Couldn't load" / "Not Found"; root causes traced to (a) /api/v1/sovereign/self returning 503 because env vars weren't populated post-handover, (b) several Sovereign endpoints (/users, /catalog, /settings, /topology) didn't exist server-side, and (c) several pages used strict-mode useParams against the mother-side /provision/$id/... route which throws Invariant on the chroot /apps, /users, /settings, /app/$id routes. Server changes: - auth.Claims gains SovereignFQDN + DeploymentID fields. - auth_handover.go authHandoverClaims gains the same; the minted Sovereign session JWT now carries them so downstream handlers can resolve identity without env or store-fallback. - sovereign_self.go reads sovereign_fqdn / deployment_id from the catalyst_session cookie payload (best-effort base64 decode; no signature check needed since this catalyst-api minted the cookie in the first place). Resolution order: env → cookie → store → 503/404. - new handlers in sovereign_more.go: GET /api/v1/sovereign/users — Keycloak realm users GET /api/v1/sovereign/catalog — embedded blueprints catalog GET /api/v1/sovereign/settings — tenant identity + features GET /api/v1/sovereign/topology — hierarchical infra view for CloudPage's getHierarchicalInfrastructure() All return well-shaped empty responses on any error (no 500s that bubble into UI error boundaries). UI changes: - SettingsPage / AppDetail / UserAccessListPage replace strict-mode useParams({ from: '/provision/$deploymentId/...' }) with useParams({ strict: false }) + useResolvedDeploymentId() fall- back. Now works on BOTH the mother route AND the chroot Sovereign route without throwing Invariant. - CatalogAdminPage's fetchApps swaps /catalog/apps → /api/v1/ sovereign/catalog when window.location.hostname is not console.openova.io. - getHierarchicalInfrastructure (CloudPage's source) swaps /api/v1/deployments/{id}/infrastructure/topology → /api/v1/ sovereign/topology under the same chroot guard. Bumps bp-catalyst-platform 1.4.49 → 1.4.50. Co-authored-by: Hati Yildiz <hatiyildiz@openova.io>		2026-05-06 16:58:00 +04:00
.claude	docs(iter-1): add IMPLEMENTATION-STATUS, fix wrong-org refs, reconcile monorepo	2026-04-27 20:43:31 +02:00
.github	fix(catalyst-build): stop auto-bumping contabo Kustomize-path image refs (#980 )	2026-05-05 21:24:57 +04:00
.playwright-mcp	feat(wizard): job dependencies SVG DAG + (stretch) timeline view (closes #206 ) (#212 )	2026-04-29 21:40:43 +02:00
clusters	fix(sovereign-console): close DoD gaps — Invariant + missing endpoints + chroot fetchers (#1044 )	2026-05-06 16:58:00 +04:00
core	fix(provisioning,catalog): parent-kustomization prefix collision + disable openclaw/stalwart-mail (#1043 )	2026-05-06 10:21:39 +04:00
docs	docs(adr): ADR-0003 RBAC ↔ NewAPI user-create hook contract (#796 ) (#807 )	2026-05-04 21:33:12 +04:00
infra/hetzner	fix(infra/hetzner): strip any-indent comments, gate user_data ≤ 30 KiB at plan-time (#966 ) (#967 )	2026-05-05 17:58:44 +04:00
platform	fix(cutover step-01): clone+push (regular repo) instead of pull-mirror (#1033 )	2026-05-06 03:19:05 +04:00
products	fix(sovereign-console): close DoD gaps — Invariant + missing endpoints + chroot fetchers (#1044 )	2026-05-06 16:58:00 +04:00
scripts	chore(bootstrap-kit): remove slot 95 bp-stalwart-sovereign (Phase-2 deferred) (#958 )	2026-05-05 15:55:30 +04:00
tests	fix(bp-newapi+services-build): imagePullSecrets on Pod, sed bumps values.yaml smeTag (#955 )	2026-05-05 15:47:37 +04:00
.gitignore	fix(bp-seaweedfs): vendor upstream chart, drop fromToml-using template (#340 ) (#504 )	2026-05-02 01:20:59 +04:00
CLAUDE.md	docs(component-count): update 53 → 56 anchors after Pass 105 (spire + nats-jetstream + sealed-secrets)	2026-04-28 13:48:24 +02:00
README.md	docs(reconcile-pass-2): align docs with ground truth at `6afdb303`	2026-04-29 11:48:57 +02:00

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.md for 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 full chart/ + blueprint.yaml per docs/IMPLEMENTATION-STATUS.md §7, plus products/axon/ and the external-dns leaf chart. The remaining 45 platform components and the cortex / fabric / fingate / relay product 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.

README.md Unescape Escape