-
Notifications
You must be signed in to change notification settings - Fork 68
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
Backups that don't trigger any jobs never complete and aren't cleaned up #1005
Labels
bug
Something isn't working
Comments
Hi @haasad The problem should now be resolved with the latest k8up version |
Unfortunately it looks like the fix does not work consistently. Some backups are correctly marked as completed (and failed) and some backups behave the same way as before.
Failed backups are correctly pruned, however only ca. 50% of the backups are marked as Failed. The remaining one keep accumulating like they did before. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Backups that don't trigger any jobs are not marked as finished. Because they aren't marked as finished they are never cleaned up and accumulate endlessly on the cluster.
Additional Context
We automatically distribute a "default" k8up schedule to new namespaces on some of our clusters. If there's no PVCs (or
BACKUP_SKIP_WITHOUT_ANNOTATION
is true) and no other means of triggering a backup job (pods withk8up.io/backupcommand
, prebackuppods etc.) the backup objects are created and never cleaned up. They accumulate endlessly.Logs
No response
Expected Behavior
Backup objects that don't trigger any jobs should be marked as finished and cleaned up like regular finished backups.
Steps To Reproduce
Version of K8up
v2.11.1
Version of Kubernetes
v1.28
Distribution of Kubernetes
OpenShift 4.15
The text was updated successfully, but these errors were encountered: