Currently when a backup job completes the pod is left in “Completed” status. In an environment where backups have to be kept for a long time the number of these pods build up and become a pain when using kubectl for other tasks.
Hi b602fa9c, I am running into the same problem, where failed or succeeded jobs linger. I also have the ‘keep’ option set, but I believe you are right that this is the retention of backups on the storage destination.
Did you ever get an answer on how to solve this problem?