The liveness probe used the default timeoutSeconds of 1. The auto-triage tick runs every minute and spends most of it waiting on Jenkins, OpenSearch, Gitea and Hermes, so against a 500m CPU limit /health occasionally answers in over a second. Three of those and the container is killed, dropping triage ticks for the length of a restart. Observed 11 times in 139 minutes, with the pod sitting 1/2 Ready and restarting repeatedly. Give both probes a 5s timeout and let liveness tolerate five failures, so a busy tick is no longer mistaken for a hung process. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
titan-iac
Flux-managed Kubernetes desired-state config for bstein.dev.
Canonical source URL:
ssh://git@scm.bstein.dev:2242/bstein/titan-iac.git
Scope
This repo contains cluster configuration consumed by Flux:
- platform/infrastructure manifests
- service manifests and kustomizations
- operational scripts for render/reconcile workflows
Apply model
I use Git + Flux as the source of truth and avoid manual in-cluster edits for durable changes.
Description
Languages
Python
60%
Shell
30.5%
Mermaid
7%
HCL
1.2%
Groovy
0.6%
Other
0.7%