Give PostgreSQL enough CPU to pass its liveness probe

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>

defaults/main.yml

@@ -17,13 +17,15 @@ gitea_valkey_resources:
     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: 100m
+    cpu: 250m
     memory: 128Mi
     ephemeral-storage: 50Mi
   limits:
-    cpu: 150m
+    cpu: "1"
     memory: 2Gi
     ephemeral-storage: 2Gi