ClaudeandClaude Opus 5.5
584779945d
Demo / hello (push) Successful in 18s
With a 150m CPU limit, pg_isready routinely exceeds the 5s probe timeout under load (e.g. Gitea's startup migration check), so the kubelet kills postgres mid-query. This is the cause of the long-running restart loop on gitea-postgresql-0. Raise the limit to one core (request 250m). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
37 lines
1.1 KiB
YAML
37 lines
1.1 KiB
YAML
#SPDX-License-Identifier: MIT-0
|
|
---
|
|
# defaults file for ansible-role-gitea
|
|
|
|
# CIDRs allowed to set X-Forwarded-For / X-Real-IP for Gitea.
|
|
# 10.244.0.0/16 is the cluster pod network, where ingress-nginx runs.
|
|
gitea_trusted_proxies: "127.0.0.0/8,::1/128,10.244.0.0/16"
|
|
|
|
# Resources for chart subcharts. These match the limits previously set by
|
|
# hand on the live StatefulSets; the bitnami default presets (192Mi) OOM.
|
|
gitea_valkey_resources:
|
|
requests:
|
|
cpu: 100m
|
|
memory: 1Gi
|
|
ephemeral-storage: 50Mi
|
|
limits:
|
|
cpu: 150m
|
|
memory: 8Gi
|
|
ephemeral-storage: 4Gi
|
|
# PostgreSQL needs real CPU: at 150m its liveness probe (pg_isready, 5s
|
|
# timeout) times out under load and the kubelet restarts it.
|
|
gitea_postgresql_resources:
|
|
requests:
|
|
cpu: 250m
|
|
memory: 128Mi
|
|
ephemeral-storage: 50Mi
|
|
limits:
|
|
cpu: "1"
|
|
memory: 2Gi
|
|
ephemeral-storage: 2Gi
|
|
|
|
# Gitea Actions runner (gitea/actions chart)
|
|
gitea_actions_enabled: true
|
|
gitea_actions_chart_version: 0.1.2
|
|
gitea_actions_runner_replicas: 1
|
|
gitea_actions_runner_token_secret: gitea-actions-runner-token
|