disable snapshots, remove scheduledbackup for snapshots #1057
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently we have ~
36000
+VolumeSnapshots
on theus-east-1
cluster in prod. This is causing the snapshot-controller to crash as it can't currently view that many objects from the Kubernetes API.Disable volume snapshots again and make sure we remove the
ScheduledBackup
along with removingVolumeSnapshots
The removal of the
VolumeSnapshots
will be done with the operator (default keeping 1 day). If every namespace has 40VolumeSnapshots
it will remove all but 1, then remove that 24 hours later after it's over 24 hours old.This adds 2 new functions
remove_scheduled_backup
andremove_snap_scheduled_backup
. This will ensure that theScheduledBackup
of typevolumeSnapshot
is removed from the namespace of the instance.