discover: repin to m12-agesort-20260901
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
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.
This commit is contained in:
parent
0f18243a64
commit
2dc00538e8
@ -64,13 +64,21 @@ configMapGenerator:
|
|||||||
|
|
||||||
# The base image `tidaldb:deploy` is the LOCAL kind-loaded tag and would
|
# The base image `tidaldb:deploy` is the LOCAL kind-loaded tag and would
|
||||||
# ImagePullBackOff on a real cluster. Pinned to the current published amd64
|
# ImagePullBackOff on a real cluster. Pinned to the current published amd64
|
||||||
# PLATFORM-manifest digest (tag m12-poisonfix-20260831), the same image the live
|
# PLATFORM-manifest digest (tag m12-agesort-20260901), the same image the live
|
||||||
# cluster set runs (k8s/cluster/statefulset.yaml:103). One image serves every
|
# cluster set runs (k8s/cluster/statefulset.yaml:103). One image serves every
|
||||||
# subcommand; the StatefulSet's `standalone` args select the mode.
|
# subcommand; the StatefulSet's `standalone` args select the mode.
|
||||||
|
#
|
||||||
|
# Bumped from m12-poisonfix-20260831 (sha256:93a2929d) because THIS profile is
|
||||||
|
# the reason the age-aware ranking work exists: on that older image `score_hot`
|
||||||
|
# read no `created_at` at all and `Sort::New` scored by raw entity id, so
|
||||||
|
# deploying discover against it would reproduce exactly the limitation the
|
||||||
|
# `NO sort:` block in schema.yaml 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. See that block's STATUS: PENDING RE-MEASUREMENT.
|
||||||
images:
|
images:
|
||||||
- name: tidaldb
|
- name: tidaldb
|
||||||
newName: registry.threesix.ai/tidal/server
|
newName: registry.threesix.ai/tidal/server
|
||||||
digest: sha256:93a2929d2473c753ed2322aac547dcc5a2d8598fd00aada5104553d7b8632078
|
digest: sha256:9234aacb197a275a67d1c1c8fbadb108e626aa48a779d4c653ad6109cda3df5a
|
||||||
|
|
||||||
labels:
|
labels:
|
||||||
# Mirrors the label k8s/kustomization.yaml applies to the base set.
|
# Mirrors the label k8s/kustomization.yaml applies to the base set.
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user