PGPool default 250m CPU request was causing scheduling failures on the single-node COULOMBCORE cluster (2 vCPU, 98% allocated). Reduced to 100m request / 200m limit — safe for a lightweight connection pooler. See INC-001: the-custodian/ops/incidents/2026-03-25-gitea-pgpool-crashloop.md Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
21 lines
618 B
YAML
21 lines
618 B
YAML
# Gitea Helm values — COULOMBCORE cluster
|
|
# Chart: gitea/gitea version: 12.5.0
|
|
# Release name: gitea namespace: default
|
|
#
|
|
# Applied via:
|
|
# helm upgrade gitea gitea/gitea --version 12.5.0 -n default -f releases/gitea/values.yaml
|
|
|
|
postgresql-ha:
|
|
pgpool:
|
|
adminPassword: changeme4 # TODO: move to sealed secret / external secret
|
|
|
|
# Right-sized for single-node COULOMBCORE (2 vCPU budget is tight).
|
|
# Default was 250m request which caused scheduling failures — see INC-001.
|
|
resources:
|
|
requests:
|
|
cpu: 100m
|
|
memory: 256Mi
|
|
limits:
|
|
cpu: 200m
|
|
memory: 384Mi
|