mirror of
https://github.com/hanzoai/bootnode.git
synced 2026-10-25 02:31:30 +00:00
zeekayandHanzo Dev
734997e46c
The lux.cloud dashboard was blank because the collector could not reach a
single validator. Two independent breaks, either one fatal:
1. It called /ext. luxd 1.36 serves /v1 only — /ext/info is 404 — and the
collector's _rpc() maps any non-200 to None, so every field came back
null with no error anywhere.
2. It dialled 15 hardcoded public LoadBalancer IPs. There are now zero
LoadBalancer Services in lux-mainnet/testnet/devnet; those IPs do not
answer at all (connect timeout, not 404).
Both are the same root defect: the observer was outside the thing it observes
and had to be told where to look. So the observer moves in. Running in lux-k8s,
a validator's address is its pod IP, read from the pod list on every
collection — there is nothing left to configure and nothing left to go stale.
Chain facts come from the node itself over /v1: info.getNodeVersion,
getNodeID, getNodeIP, peers, isBootstrapped per chain, eth_blockNumber at
/v1/bc/C/rpc (the bc/ segment is load-bearing; /v1/C/rpc is not a route) and
platform.getHeight at /v1/bc/P, which quotes its integer.
That also collapses the MODE A / MODE B split: there is one path, not two.
Two corrections to what the old collector reported:
version is now what the fleet RUNS, not what the CR declares. The mainnet
LuxNetwork CR asks for ghcr.io/luxfi/node:v1.34.0, a tag that does not
exist; the nodes are on luxd/1.36.2. The dashboard must show the running
truth, so observation wins and image keeps the declared value.
external_ip becomes ip, matching console/lib/fleet.ts, and carries the
address the node advertises for itself (info.getNodeIP) rather than an
address someone wrote down.
Degraded is reported as degraded. A node that does not answer keeps every
field null and counts against nodes_rpc_ok; it is never smoothed over.
Placement: this stays in hanzoai/bootnode rather than folding into
hanzoai/cloud. cloud is not deployed on lux-k8s, and standing the whole
monolith up inside the chain cluster to run a read-only collector is a far
larger change than the collector itself. The surface is registered with zip's
Group; the route set is unchanged.
Deploy: Deployment/Service/RBAC in lux-k8s (lux-fleet.yaml, read-only —
list/get on pods and luxnetworks, no pods/proxy, no exec). The public URL
resolves to bootnode-k8s, so that cluster forwards just /v1/fleets/lux across
(lux-fleet-bridge.yaml); no other path on the host is touched.
Tests: a luxd stub that 404s anything outside /v1 and quotes platform height;
assertions that every probe path is under /v1, that no wire key is ever
omitted (an absent key reads as undefined and blanks a cell), that a down node
stays null, and that /v1/fleets/lux/zzzz is 404 next to a 200 on /overview.
Co-authored-by: Hanzo Dev <[email protected]>
73 lines
1.9 KiB
YAML
73 lines
1.9 KiB
YAML
# The bootnode-k8s half of the fleet API.
|
|
#
|
|
# api.cloud.lux.network resolves to bootnode-k8s, but the collector has to run
|
|
# in lux-k8s to see the fleet (see lux-fleet.yaml). So on this side the
|
|
# lux-fleet Service keeps its name and its ingress path and stops selecting
|
|
# pods: its endpoint is the lux-k8s ingress load balancer, a stable address,
|
|
# reached over HTTPS with the original Host header intact.
|
|
#
|
|
# Only /v1/fleets/lux crosses. Every other api.cloud.lux.network path is served
|
|
# by web3-platform-api in this cluster and is not touched.
|
|
#
|
|
# Apply to: do-sfo3-bootnode-k8s.
|
|
|
|
---
|
|
apiVersion: v1
|
|
kind: Service
|
|
metadata:
|
|
name: lux-fleet
|
|
namespace: bootnode
|
|
labels:
|
|
app: lux-fleet
|
|
spec:
|
|
type: ClusterIP
|
|
# No selector: the endpoints are declared below, not derived from pods here.
|
|
ports:
|
|
- name: http
|
|
port: 80
|
|
|
|
---
|
|
apiVersion: discovery.k8s.io/v1
|
|
kind: EndpointSlice
|
|
metadata:
|
|
name: lux-fleet-luxk8s
|
|
namespace: bootnode
|
|
labels:
|
|
kubernetes.io/service-name: lux-fleet
|
|
addressType: IPv4
|
|
ports:
|
|
- name: http
|
|
port: 443
|
|
protocol: TCP
|
|
endpoints:
|
|
# do-sfo3-lux-k8s ingress load balancer (lux-system/hanzo-ingress).
|
|
- addresses: ["134.199.138.27"]
|
|
conditions:
|
|
ready: true
|
|
|
|
---
|
|
apiVersion: networking.k8s.io/v1
|
|
kind: Ingress
|
|
metadata:
|
|
name: lux-fleet
|
|
namespace: bootnode
|
|
annotations:
|
|
# The endpoint above is a TLS listener; it presents a certificate for a
|
|
# name it does not own, which is fine because routing is by Host.
|
|
nginx.ingress.kubernetes.io/backend-protocol: HTTPS
|
|
nginx.ingress.kubernetes.io/proxy-ssl-verify: "off"
|
|
nginx.ingress.kubernetes.io/proxy-read-timeout: "30"
|
|
spec:
|
|
ingressClassName: nginx
|
|
rules:
|
|
- host: api.cloud.lux.network
|
|
http:
|
|
paths:
|
|
- path: /v1/fleets/lux
|
|
pathType: Prefix
|
|
backend:
|
|
service:
|
|
name: lux-fleet
|
|
port:
|
|
number: 80
|