174ca02aba
Adds a tenant-aware branding layer to the marketplace so the same pods can serve marketplace.openova.io (default OpenOva, dark) and omantel.openova.io (Omantel logo, forced light theme) — no extra deployments, no extra resources. Tomorrow's Omantel demo lands on omantel.openova.io and gets the partner look without disturbing the existing marketplace.openova.io experience. Changes - src/lib/tenant.ts: hostname → tenant config (logo, brand, force theme, skip-console-redirect). Easy to extend with future partner hosts. - src/layouts/Layout.astro: pre-hydration script sets <html data-tenant> and forces light theme for omantel before paint (zero flash). Returning- user redirect to console.openova.io/nova is suppressed for tenants with skipConsoleRedirect=true so the demo stays on the partner host. - src/components/Header.svelte: renders both brand spans; CSS in global.css hides the inactive one based on html[data-tenant]. SSR'd HTML stays cacheable across hostnames. - public/logos/omantel.svg: official Omantel wordmark (Wikimedia source, brand colours #283d90 navy + #e27739 orange). Ingress + chart fixes - products/catalyst/chart/templates/sme-services/ingress.yaml: adds two ingresses (omantel /api/ priority 200, omantel / priority 100) pointing at the existing gateway/marketplace services. cert-manager issues omantel-tls via letsencrypt-prod (DNS already resolves via the *.openova.io wildcard A record). - products/catalyst/chart/templates/sme-services/marketplace.yaml: this path is Kustomize-applied (contabo-mkt only — Sovereigns skip via .helmignore), so the image must be a concrete string. PR #580 templated it with Helm syntax which produced InvalidImageName on the new ReplicaSet — rolling forward stalled. De-templatized and pinned to the current deployed SHA so the marketplace-build CI sed can update it. Backwards compatibility - marketplace.openova.io: identical render — default tenant 'openova', inline OpenOva SVG, dark theme by default, console redirect intact. - Other hosts (console.openova.io, admin.openova.io): untouched. Co-authored-by: hatiyildiz <269457768+hatiyildiz@users.noreply.github.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| admin | ||
| cmd/cert-manager-dynadot-webhook | ||
| console | ||
| marketplace | ||
| marketplace-api | ||
| pkg/dynadot-client | ||
| pool-domain-manager | ||
| services | ||
| README.md | ||
Catalyst Control Plane (core/)
The user-facing Catalyst control plane modules. Status: Consolidated and deployed on Catalyst-Zero (Contabo k3s) as of Pass 105 (2026-04-28).
Read first:
docs/PROVISIONING-PLAN.md,docs/GLOSSARY.md,docs/ARCHITECTURE.md,docs/IMPLEMENTATION-STATUS.md.
What this is
The four modules that constitute the Catalyst control plane's user-facing surface, plus the Go backend they share. Each is its own Containerfile-built workload, deployed on every Catalyst Sovereign (starting with Catalyst-Zero on Contabo, and on every franchised Sovereign provisioned thereafter).
| Module | Stack | Purpose | Deployed image |
|---|---|---|---|
console/ |
Astro + Svelte | Primary user-facing UI. Form / Advanced / IaC editor depths. The Sovereign-provisioning wizard at /sovereign (Phase 3) lives here. |
ghcr.io/openova-io/openova/console:<sha> |
admin/ |
Astro + Svelte | Sovereign-admin operations UI. Includes the canonical voucher / billing / catalog / orders / tenants admin surface that sovereign-admin uses to issue vouchers to franchised tenants. | ghcr.io/openova-io/openova/admin:<sha> |
marketplace/ |
Astro + Svelte | Public-facing Blueprint card grid (the "App Store"). 5-step Plan → Apps → Addons → Checkout → Review flow. |
ghcr.io/openova-io/openova/marketplace:<sha> |
marketplace-api/ |
Go | Backend API for marketplace and console. Handlers (handlers/), provisioner (provisioner/), store (store/). Phase 4 extends this with full Hetzner provisioning. |
ghcr.io/openova-io/openova/marketplace-api:<sha> |
The Helm chart that deploys all four (plus catalyst-ui, catalyst-api, and the legacy SME backend services) lives at products/catalyst/chart/.
CI / Build
Each module has a corresponding GitHub Actions workflow:
.github/workflows/console-build.yaml.github/workflows/admin-build.yaml.github/workflows/marketplace-build.yaml.github/workflows/marketplace-api-build.yaml.github/workflows/catalyst-build.yaml— coversproducts/catalyst/bootstrap/{ui,api}/(the React SPA + Go bootstrap API)
Each workflow watches its module path, builds the Containerfile, pushes to GHCR with a SHA tag, and pins the SHA into the corresponding manifest in products/catalyst/chart/templates/ (so Flux on Catalyst-Zero picks up the new image on the next reconciliation).
Migration history
- Pass 105 (2026-04-28):
console/,admin/,marketplace/consolidated fromopenova-private/apps/{console,admin,marketplace}/into this directory.marketplace-api/consolidated fromopenova-private/website/marketplace-api/. Six CI workflows migrated to.github/workflows/of the public repo. Catalyst-Zero K8s manifests migrated fromopenova-private/clusters/contabo-mkt/apps/{catalyst,sme/services,marketplace-api}/intoproducts/catalyst/chart/templates/. Image references updated fromghcr.io/openova-io/openova-private/sme-{admin,console,marketplace}toghcr.io/openova-io/openova/{admin,console,marketplace}. The 8 legacy SME backend services (auth,billing,catalog,domain,gateway,notification,provisioning,tenant) keep theiropenova-private/sme-*image refs until their source code migrates in a follow-up phase.
Part of OpenOva