velero-io/velero

Garbage collect download/serverstatus/deletebackup requests

Open

#5,683 opened on Dec 13, 2022

View on GitHub
 (2 comments) (2 reactions) (1 assignee)Go (1,550 forks)auto 404
Help wantedbacklogkind/tech-debt

Repository metrics

Stars
 (10,111 stars)
PR merge metrics
 (PR metrics pending)

Description

Describe the problem/challenge you have [A description of the current limitation/problem/challenge that you are experiencing.] If there was an invalid download requests, the object remains in the cluster forever until that request ever become valid. If download request from logs/describe command work after a week, a user has likely moved on. It can get annoying at times to see errors relating to old downloadrequests that obviously have no use to be there any longer.

Describe the solution you'd like [A clear and concise description of what you want to happen.] Introduce default time to live TTL for download requests relating to logs or describe commands and deleting it after some time, maybe a day or an hour.

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Environment:

  • Velero version (use velero version):
  • Kubernetes version (use kubectl version):
  • Kubernetes installer & version:
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

  • :+1: for "The project would be better with this feature added"
  • :-1: for "This feature will not enhance the project in a meaningful way"

Contributor guide