Both names answered 404 at every path: the declaration that served them
(k8s/lux-k8s/cdn/cdn.yaml) addressed an in-cluster S3 bucket on DOKS, and that
account is suspended. DNS and the tunnel already deliver both to the ingress --
each returns the ingress's own "404 page not found" -- so what was missing was a
route, not a path to the cluster.
deploy/lux-cdn/lux-cdn.yaml is that route, on the same pattern as every other
static host here: one staticFiles middleware over s3://hanzo-sites/lux/lux-cdn,
one rule matching both names, and no Deployment, because a static host is not a
pod. luxfi/cdn publishes the prefix from its own lane.
NO spaMode, and that is the one place this differs from the sites beside it.
The exchange's rule is that a mark which exists nowhere is reported missing and
never drawn, and that only holds if the host says so: in SPA mode an unknown
path answers 200 with index.html, so a caller asking for a PNG receives an HTML
document, caches it, and reports nothing.
The prefix is lux/lux-cdn rather than lux/cdn because `cdn` is on cloud's
reserved-label list beside api, admin and gateway -- no site may be published at
cdn.<apex> and shadow real infrastructure -- so that slug cannot be created and
the prefix cannot be published to.
assets.lux.network keeps its own declaration in that directory until it moves.
Co-authored-by: Hanzo Dev <[email protected]>
zeekayandHanzo Dev
1de35d7464