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

Implement successfulBackupsHistoryLimit and failedBackupsHistoryLimit in EtcdBackupSchedule #105

Open
adamhosier opened this issue Nov 28, 2019 · 0 comments

Comments

@adamhosier
Copy link
Contributor

We would like to limit the amount of successful/failed EtcdBackup resources that are lying around in clusters.

The EtcdBackupSchedule controller should be adjusted to remove all but the x newest EtcdBackup resources that it was responsible for creating. This should be configurable to be different for successful/failed backups.

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