Cleanup maintenance job pods in Competed state

[insider89]

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

[kiku99]

Hi @jenting ,

I’d like to take a stab at fixing this issue. Before I start, could you confirm if anyone is already working on it, or share any pointers about what you’d prefer for the solution approach?

Thanks!

[insider89]

I am not working on it.