#510 remove double volume type spec #511
Merged
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.
Closes #510
Implemented solution: see task #510 description
How to test this PR: deployments are affected by this change only if backups are enabled. Spin up a deployment with at least one database and enabled backups on GCP and verify that pods and cron jobs are not deadlocking.
Sanity checks:
Breaking changes (select one):
breaking-change
Possible deployment updates issues (select one):
alert:deployment
The backup volumes are redefined so the new specification will clash with the old one and the backup volume db-backups may need to be removed and recreated.
Test coverage (select one):
Documentation (select one):
Nice to have (if relevant):