feat: run FuzeFront in-cluster on FuzeInfra (kind), first light - #8
Merged
Conversation
Points FuzeInfra at 70c0158 (Helm chart + kind local cluster + EKS terraform). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Native enums (004/005/006) reference pre-created types via existingType:true (knex was calling .join on null allowed-values and crashing) - Drop the duplicate sessions(tenant_id) index in 007 (already created in 003) - Inline the password literal in 008 (Postgres DDL rejects bound params) - Add backend/.dockerignore to keep host node_modules out of the build context Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Wire Tailwind v4: @tailwindcss/postcss plugin, @import 'tailwindcss', @theme inline token mapping (shadcn) — was half-migrated and unbuildable - Build stage on node:20-bookworm-slim (glibc) so @tailwindcss/oxide resolves - Re-export the standalone api functions/types components import (api.ts had been refactored into *API objects, breaking ~9 components) - Add frontend/.dockerignore Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…uster (kind) - deploy/helm/fuzefront: backend+frontend Deployments/Services/Ingress/Secret, wired to FuzeInfra services via cross-namespace CoreDNS (postgres.fuzeinfra.svc) - deploy/fuzeinfra-lean-values.yaml: bring up only Postgres+Redis for first light - README runbook; .prettierignore protects the Helm templates Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings FuzeFront up in-cluster against the k8s-migrated FuzeInfra, and gets the microfrontend platform to first light: the host shell serves, the backend connects to FuzeInfra's Postgres, and an app can self-register and load at runtime (no compile-time knowledge of the host beyond the SDK).
What's here
deploy/helm/fuzefront): backend + frontend Deployments/Services/Ingress/Secret, wired to FuzeInfra via cross-namespace CoreDNS (postgres.fuzeinfra.svc). Lean FuzeInfra overlay (deploy/fuzeinfra-lean-values.yaml) brings up just Postgres+Redis. Runbook in the chart README.existingType, duplicatesessions(tenant_id)index, parameterized-DDL in the user migration.api.tsexports ~9 components import.Verified
/api/healththrough ingress → frontend nginx → backend → Postgres:ok, connectedPOST /api/apps/register→ 201, persisted (canonicalmodule-federationtype)Deferred (follow-ups)
Authentik (OIDC), Permit (PDP), dedicated
fuzefront_userDB role, demo seeds. kind needs node imagev1.34+ ingress-nginxcontroller-v1.11.2on this host (noted for FuzeInfra's setup-kind.sh).