tidaldb/k8s/discover
jordan 2dc00538e8
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
discover: repin to m12-agesort-20260901
The discover profile is the reason the age-aware ranking work exists, but its
kustomization still pinned m12-poisonfix-20260831 (sha256:93a2929d) -- the image
on which score_hot reads no created_at at all and Sort::New scores by raw entity
id. Deploying it against that digest would reproduce exactly the limitation its
own NO sort: block documents.

Necessary but not sufficient: cold-start still ties because hot's
log10(max(views,1)) numerator is exactly 0.0 at 0 or 1 views, so the NO sort:
decision stands and its STATUS: PENDING RE-MEASUREMENT is unchanged.

No deployment performed. The StatefulSet stays replicas: 0 and targets ns
thepeach-staging, which does not exist on orchard9-k3sf (zero *peach* namespaces);
its base image comment says tidaldb:deploy is kind-loaded, so this is a local
target, not a fleet one.
2026-08-31 23:12:08 -06:00
..
kustomization.yaml discover: repin to m12-agesort-20260901 2026-08-31 23:12:08 -06:00
poddisruptionbudget.yaml ranking: make Hot and New age-aware; fix the same gap in three more places 2026-08-31 19:58:01 -06:00
schema.yaml ranking: fix two BLOCKERs in the age-aware sorts, and stop trusting created_at units 2026-08-31 21:31:31 -06:00
service.yaml ranking: make Hot and New age-aware; fix the same gap in three more places 2026-08-31 19:58:01 -06:00
statefulset-patch.yaml ranking: make Hot and New age-aware; fix the same gap in three more places 2026-08-31 19:58:01 -06:00
statefulset.yaml ranking: make Hot and New age-aware; fix the same gap in three more places 2026-08-31 19:58:01 -06:00