tidaldb/k8s/cluster
jordan cc7066e0d8 k8s(cluster): pin the boot-pull-fix image now running on all three voters
registry.threesix.ai/tidal/server:m12-boot-pull-fix-20260821
@sha256:4150af1044b8084b84abeafedbbaedb1f084a2c84fd0600b56f5b04ed0697eba

Rolled tidaldb-0/-1/-2 onto it via OnDelete with a quorum write probe between each
step: every probe returned 201, so the roll cost zero write availability. Cluster
is 3/3 with all nine group-replicas converged on identical frontiers
(13322227/13540667/13072512) and an identical 33,331-vector corpus. PDB
disruptionsAllowed is back to 1 after being 0 for the whole incident.
updateStrategy restored to RollingUpdate/partition 0.
2026-08-21 12:01:34 -06:00
..
certs.yaml fix(m12p6): complete T4 TLS scale-up — two-tier PKI + join_boot grpc_tls fallback 2026-06-14 22:41:59 -06:00
kustomization.yaml feat(m11): cluster security (m11p7) + perf instrumentation floor 2026-06-13 01:25:35 -06:00
namespace.yaml feat(m11): membership, snapshot install, and reseed (m11p5) 2026-06-12 19:55:54 -06:00
poddisruptionbudget.yaml feat(m11): membership, snapshot install, and reseed (m11p5) 2026-06-12 19:55:54 -06:00
schema-configmap.yaml bench(1536): production-shape capacity — read path is cheap, quorum write is the ceiling 2026-06-13 21:40:58 -06:00
secret.example.yaml feat(m11): cluster security (m11p7) + perf instrumentation floor 2026-06-13 01:25:35 -06:00
service-client.yaml feat(m11): membership, snapshot install, and reseed (m11p5) 2026-06-12 19:55:54 -06:00
service-peers.yaml feat(m12p4): sharded ingestion — scatter-gather pool + cross-shard unified reads (L4) 2026-06-14 15:17:35 -06:00
statefulset.yaml k8s(cluster): pin the boot-pull-fix image now running on all three voters 2026-08-21 12:01:34 -06:00
topology-configmap.yaml feat(m12p4): sharded ingestion — scatter-gather pool + cross-shard unified reads (L4) 2026-06-14 15:17:35 -06:00