fix(k8s): give api verifier capacity
All checks were successful
CD Pipeline / workflow-shape (push) Successful in 1s
CD Pipeline / cancel-stale-cd (push) Has been skipped
CD Pipeline / tests (push) Successful in 5m2s
CD Pipeline / build-and-deploy (push) Successful in 9m57s
CD Pipeline / post-deploy-checks (push) Successful in 2m4s

This commit is contained in:
ogt
2026-07-14 16:54:36 +08:00
parent 7625cb9b0c
commit 7eb19037cf
2 changed files with 16 additions and 2 deletions

View File

@@ -297,6 +297,18 @@ def test_cd_uses_live_spec_rollback_and_non_mutating_post_verifier() -> None:
)
def test_api_has_capacity_for_the_production_concurrency_verifier() -> None:
container = _deployment_container(
"k8s/awoooi-prod/06-deployment-api.yaml",
"api",
)
assert container["resources"] == {
"requests": {"cpu": "500m", "memory": "512Mi"},
"limits": {"cpu": "2", "memory": "1Gi"},
}
def test_cd_workload_db_identity_retries_transient_worker_rollout_race(
tmp_path: Path,
) -> None:

View File

@@ -279,10 +279,12 @@ spec:
mountPath: /tmp/awoooi-prometheus-multiproc
resources:
requests:
cpu: "200m"
# The production 8-way read verifier saturated the former 1-core
# limit and caused liveness restarts despite ample node/quota headroom.
cpu: "500m"
memory: "512Mi"
limits:
cpu: "1"
cpu: "2"
memory: "1Gi"
livenessProbe:
httpGet: