Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cleanup maintenance job pods in Competed state #628

Open
insider89 opened this issue Nov 15, 2024 · 0 comments
Open

Cleanup maintenance job pods in Competed state #628

insider89 opened this issue Nov 15, 2024 · 0 comments

Comments

@insider89
Copy link

insider89 commented Nov 15, 2024

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.
Screenshot 2024-11-15 at 14 34 22
Screenshot 2024-11-15 at 16 01 24

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant