zeekayandHanzo Dev c23995b3e8 the demo keeps nothing, so it claims nothing
A 20Gi RWO claim takes local-path on k3s, which puts the volume on one
node and pins the pod there — the image is a multi-arch index and the
claim was the only reason it never ran on the other node.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-16 17:28:09 -07:00
2026-09-08 23:59:46 -07:00
2026-09-08 15:23:20 -07:00
2026-09-08 23:59:46 -07:00
2026-09-08 15:23:20 -07:00
2026-07-26 15:46:04 -07:00
2026-09-08 23:59:46 -07:00
2026-09-08 15:23:20 -07:00
2026-09-08 15:23:20 -07:00
2026-09-08 15:23:20 -07:00
2026-09-08 15:23:20 -07:00
2026-09-08 23:59:46 -07:00
2026-09-08 15:23:20 -07:00
2026-09-08 15:23:20 -07:00

Lux Universe — retired

Read-only from here. Canonical: https://git.hanzo.ai/lux/universe

This tip is an ancestor of canonical main, so no commit reachable from this branch is unique to it — the canonical repo is a strict superset. Nothing was lost by stopping here.

Two universes for one org is a split brain: a push lands somewhere real, reports success, and never reaches a cluster, because CD reconciles the other one (deploy/applicationset.yaml names the canonical URL). One repo per org means that failure cannot happen.

S
Description
Declared state for the lux fleet: one values file per service, one ApplicationSet
Readme BSD-3-Clause
6.7 MiB
Languages
TypeScript 66.4%
Shell 14.9%
Python 7.9%
Go 4.8%
Makefile 4.3%
Other 1.7%