bikoret

0 Fork 0

Files

T

Scott KarpandClaude Fable 5.1 7e1a4473c7 deployment: replace in place — one replica, one node, no room to surge (tablet 31)

The default RollingUpdate (maxSurge 25% → one extra pod) needs 450m CPU
beside the running pod; the node has 1700m allocatable and 1470m
requested. The Tablet-30 rollout sat Pending for five minutes while the
old image kept serving. maxSurge 0 / maxUnavailable 1: the old pod goes
first, the new one schedules, and is Ready once the kohen writes manna.
Patched live 2026-10-04; this makes the manifest match.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

2026-10-04 16:48:19 +00:00

cert-manager-issuer.yaml

Fix MCP connector: cert-manager URL typo and TCP probes

2026-04-17 14:53:30 -04:00

configmap.yaml

build: four amd64 images that RUN — JIT segfault, build context, and four dead vessels

2026-08-23 12:30:36 -04:00

deployment.yaml

deployment: replace in place — one replica, one node, no room to surge (tablet 31)

2026-10-04 16:48:19 +00:00

gitea-mcp-deployment.yaml

Fix gitea-mcp env: use GITEA_ACCESS_TOKEN, not GITEA_TOKEN