Drop lux-mainnet work-board: a second copy nothing routes to

work.hanzo.network is served by hanzo-mainnet/work-board and answers 200. This
deployment carries the same image behind a Service with no Ingress, and
work.lux.network answers 404 — so it has taken a pod and an amd64 node slot
without ever having a caller.

Co-authored-by: Hanzo Dev <[email protected]>

deploy/lux-mainnet/work-board.yaml

@@ -1,61 +0,0 @@
-# Generated from the live lux-mainnet/work-board Deployment on do-sfo3-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: 2
-selectorLabels:
-  app: work-board
-image:
-  repository: ghcr.io/luxfi/work-board
-  tag: lux-34afd2d
-  pullPolicy: IfNotPresent
-resources:
-  limits:
-    memory: 128Mi
-  requests:
-    cpu: 10m
-    memory: 32Mi
-livenessProbe:
-  failureThreshold: 3
-  httpGet:
-    path: /
-    port: 3000
-    scheme: HTTP
-  initialDelaySeconds: 10
-  periodSeconds: 20
-  successThreshold: 1
-  timeoutSeconds: 1
-readinessProbe:
-  failureThreshold: 3
-  httpGet:
-    path: /
-    port: 3000
-    scheme: HTTP
-  initialDelaySeconds: 3
-  periodSeconds: 10
-  successThreshold: 1
-  timeoutSeconds: 1
-ports:
-- containerPort: 3000
-  name: http
-  servicePort: 80
-imagePullSecrets:
-- name: ghcr-luxfi
-rollingUpdate:
-  maxSurge: 25%
-  maxUnavailable: 25%
-topologySpread:
-  enabled: false
-lifecycle: null
-terminationGracePeriodSeconds: 30
-
-# 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 — 678 restarts. 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