vmware-tanzu/helm-charts
Cleanup maintenance job pods in Competed state
Offen
#628 geöffnet am 15.11.2024
good first issuevelero
Repository-Metriken
- Stars
- (312 Sterne)
- PR-Merge-Metriken
- (PR-Metriken ausstehend)
Beschreibung
What steps did you take and what happened: Maintenance Job running very frequently and we have a lot of pods in Completed state. I don't see any parameters I can provide to cleanup it.
What did you expect to happen:
Helm chart should allow to set ttlSecondsAfterFinished parameter for maintenance job.
The output of the following commands will help us better understand what's going on:
repositoryMaintenanceJob:
requests:
# cpu: 500m
# memory: 512Mi
limits:
# cpu: 1000m
# memory: 1024Mi
# Number of latest maintenance jobs to keep for each repository
latestJobsCount: 3
Anything else you would like to add:
Add new ttlSecondsAfterFinished to the repositoryMaintenanceJob would be helm to keep env clean.
Environment:
- helm version (use
helm version): 3.16 - helm chart version and app version (use
helm list -n <YOUR NAMESPACE>): 8.0.0 - Kubernetes version (use
kubectl version): 1.30.5 - Kubernetes installer & version: 1.30.5
- Cloud provider or hardware configuration: GKE/AWS/Azure
- OS (e.g. from
/etc/os-release): Linux