vrr/cozystack
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(etcd): add protective limits to defrag CronJob

Browse source 
Without concurrencyPolicy and job limits, the defrag CronJob can
accumulate hundreds of running/failed pods during cluster upgrades
when etcd is temporarily unavailable. This was observed after
upgrading to v1.1.2 where defrag jobs piled up across tenants.

Assisted-By: Claude AI
Signed-off-by: Kirill Ilin <stitch14@yandex.ru>
This commit is contained in:
Kirill Ilin 2026-03-17 13:21:28 +05:00
parent 9fb9354fd2
commit ed8ba3beec
No known key found for this signature in database
GPG key ID: E902D8B383F7675E
1 changed files with 5 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

5
packages/extra/etcd/templates/etcd-defrag.yaml
View file

@ -4,9 +4,14 @@ metadata:
name: {{ .Release.Name }}-defrag
spec:
schedule: "0 * * * *"
concurrencyPolicy: Forbid
startingDeadlineSeconds: 300
successfulJobsHistoryLimit: 3
failedJobsHistoryLimit: 1
jobTemplate:
spec:
activeDeadlineSeconds: 1800
backoffLimit: 2
template:
spec:
containers: