zeekay
51460827d4
The two mains shared no history, so this is a per-file three-way merge:
for each file the 65 forge-only commits touched (by patch-id), the base is
the newest version both histories held. 105 files merged or took one side
cleanly, 48 were already identical, and the 45 true conflicts and 31
modify/delete pairs were resolved by what runs on the cluster:
- The forge wins where it is live: explorer 1.5.56 (digest 45db11ff) and
its archive readers, explore-fe-hanzo's ConfigMap env (AI coin,
/v1/indexer/hanzo, /v1/chain/hanzo/rpc), exchange-api reading
luxd-archive, and explore-fe-{lux,zoo}-testnet, pinned to what they run
(v2.8.5-lux / v2.8.4-lux).
- GitHub wins where it is live: explore-fe-lux v2.8.5-lux, explore-fe-zoo
v2.8.4-lux, bankd v1.0.18, lux-build's routes.
- The forge's retirement of workloads that run nowhere stands: lux-mainnet
dex, lux-hb2, lux-market, traffic, wallet-web; the lux-testnet frontends,
indexer, exchange and gateways; lux-operator. deploy/lux-testnet/luxd.yaml
stays, since roll_luxd.sh reads it.
- GitHub's deletions stand: lux-finance and lux-financial (static sites
now), the k8s/ operator manifests, .hanzo/workflows/cicd.yml.
- Paths are /v1/chain/C/rpc where the forge had written /v1/chain/c. All
four spellings answer; this one is the documented form. The forge's
/{network}/v1 doc lines are dropped: a network is a host, and the prefix
404s.
Dry-run against the running objects (server-side, as CD applies), the
merged explorer shows no change where GitHub's showed 152 lines, and no
other live workload moves further from what runs. Every deploy/*/*.yaml
renders with charts/app; price.yaml, which failed on GitHub, now renders.
Claude-Session: https://claude.ai/code/session_01TzirYkGmD88w4GipqivUtV
121 lines
3.1 KiB
YAML
121 lines
3.1 KiB
YAML
# Generated from the live lux-mainnet/lux-build Deployment on lux-k8s
|
|
# by hack/live2values.py. Live is the source: a repo of hand-applied
|
|
# manifests has unknown currency, the running fleet does not.
|
|
replicas: 1
|
|
selectorLabels:
|
|
app: lux-build
|
|
containerName: build
|
|
image:
|
|
repository: ghcr.io/luxfi/build
|
|
tag: 0.1.14
|
|
pullPolicy: IfNotPresent
|
|
env:
|
|
- name: NODE_ENV
|
|
value: production
|
|
- name: NEXT_TELEMETRY_DISABLED
|
|
value: '1'
|
|
resources:
|
|
limits:
|
|
cpu: 500m
|
|
memory: 512Mi
|
|
requests:
|
|
cpu: 100m
|
|
memory: 256Mi
|
|
livenessProbe:
|
|
failureThreshold: 3
|
|
httpGet:
|
|
path: /v1/health
|
|
port: 3000
|
|
scheme: HTTP
|
|
initialDelaySeconds: 10
|
|
periodSeconds: 30
|
|
successThreshold: 1
|
|
timeoutSeconds: 1
|
|
readinessProbe:
|
|
failureThreshold: 3
|
|
httpGet:
|
|
path: /v1/health
|
|
port: 3000
|
|
scheme: HTTP
|
|
initialDelaySeconds: 5
|
|
periodSeconds: 10
|
|
successThreshold: 1
|
|
timeoutSeconds: 1
|
|
ports:
|
|
- containerPort: 3000
|
|
imagePullSecrets:
|
|
- name: ghcr-luxfi
|
|
rollingUpdate:
|
|
maxSurge: 25%
|
|
maxUnavailable: 25%
|
|
topologySpread:
|
|
enabled: false
|
|
lifecycle: null
|
|
terminationGracePeriodSeconds: 30
|
|
|
|
# Enforcement switch, read by the lux-fleet ApplicationSet's templatePatch --
|
|
# not by the chart. selfHeal returns a hand-edited object to what is written
|
|
# here; prune stays off, so nothing is ever deleted.
|
|
cd:
|
|
automated: false
|
|
|
|
# The edge, lifted out of k8s/lux-mainnet/lux-build.yaml.
|
|
#
|
|
# The Deployment and Service were declared here and the IngressRoute was not, so
|
|
# the half of this service a user actually reaches — lux.build, and the two hosts
|
|
# that redirect to it — sat outside CD entirely. The chart passes `spec` through
|
|
# verbatim, so these are the live objects, not a restatement of them.
|
|
routes:
|
|
- name: lux-build
|
|
spec:
|
|
entryPoints:
|
|
- websecure
|
|
routes:
|
|
- match: Host(`lux.build`)
|
|
kind: Rule
|
|
services:
|
|
- name: lux-build
|
|
port: 3000
|
|
- match: Host(`www.lux.build`)
|
|
kind: Rule
|
|
middlewares:
|
|
- name: redirect-www-lux-build
|
|
services:
|
|
- name: lux-build
|
|
port: 3000
|
|
- match: Host(`build.lux.network`)
|
|
kind: Rule
|
|
middlewares:
|
|
- name: redirect-to-lux-build
|
|
services:
|
|
- name: lux-build
|
|
port: 3000
|
|
# The edge's own certificate answers; Cloudflare fronts every name.
|
|
tls: {}
|
|
|
|
middlewares:
|
|
- name: redirect-to-lux-build
|
|
spec:
|
|
redirectRegex:
|
|
regex: ^https://build\.lux\.network/(.*)
|
|
replacement: https://lux.build/${1}
|
|
permanent: true
|
|
- name: redirect-www-lux-build
|
|
spec:
|
|
redirectRegex:
|
|
regex: ^https://www\.lux\.build/(.*)
|
|
replacement: https://lux.build/${1}
|
|
permanent: true
|
|
|
|
# One amd64 manifest, so evo is the only node that can execute this. spark
|
|
# registers qemu-x86_64 binfmt, which is worse than a refusal: the pod starts,
|
|
# runs emulated, and faults at random — containerd refuses the index outright and it sits in ImagePullBackOff. Stated rather than left
|
|
# to the scheduler, the same way trade.yaml states it. The toleration keeps the
|
|
# pin working if `hanzo.ai/no-ci` goes back on evo.
|
|
nodeSelector:
|
|
kubernetes.io/arch: amd64
|
|
tolerations:
|
|
- key: hanzo.ai/no-ci
|
|
operator: Exists
|
|
effect: NoSchedule
|