ClaudeandClaude Opus 5.5 b81a2d64d0 Pin valkey/postgresql resources; harden runner token step ...

The live valkey and postgresql StatefulSets had memory limits raised by
hand (8Gi and 2Gi). A helm upgrade reverts those to the bitnami 192Mi
preset, and valkey then OOMs loading its ~3.3GB dataset. Move the limits
into role defaults so upgrades keep them.

Generate the runner token with kubectl exec against the deployment after
waiting for its rollout, with retries, instead of kubernetes.core.k8s_exec
(the control plane's kubernetes python client is too old for it).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-11-06 13:05:10 -05:00

..

.actions.yaml.swp

Initial commit

2026-02-27 17:30:50 -05:00

actions.yaml

Pin valkey/postgresql resources; harden runner token step

2026-11-06 13:05:10 -05:00

gitea.yaml

Pin valkey/postgresql resources; harden runner token step

2026-11-06 13:05:10 -05:00

main.yml

Log real client IPs and enable Gitea Actions with a runner

2026-11-06 12:56:58 -05:00

mcp.yaml

Update

2026-10-23 11:23:04 -04:00