You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
At the moment the script for uploading to GoogleStorageBucket is using the "-d" option so the files in the bucket get deleted! Instead this should be done by the Lifycycle management of the Google Storage Bucket.
Version of Helm and Kubernetes:
not relevant
Helm Version:
not relevant
Kubernetes Version:
not relevant
Which version of the chart:
4.0.2
What happened:
Files get deleted by rsync command.
What you expected to happen:
Files should not get deleted or at least this should be editable.
Then I could use "housekeeping" that my PVC will not grow size and also use the GCP "lifecycle" to manage how many backup files I want to keep in the Google Storage Bucket.
How to reproduce it (as minimally and precisely as possible):
<~--
This could be something like:
values.yaml (only put values which differ from the defaults)
key: value
helm install my-release {{ .GitHubOrg }}/name-of-chart --version version --values values.yaml
-->
Anything else we need to know:
The text was updated successfully, but these errors were encountered:
Describe the bug
At the moment the script for uploading to GoogleStorageBucket is using the "-d" option so the files in the bucket get deleted! Instead this should be done by the Lifycycle management of the Google Storage Bucket.
Version of Helm and Kubernetes:
not relevant
Helm Version:
not relevant
Kubernetes Version:
not relevant
Which version of the chart:
4.0.2
What happened:
Files get deleted by rsync command.
What you expected to happen:
Files should not get deleted or at least this should be editable.
Then I could use "housekeeping" that my PVC will not grow size and also use the GCP "lifecycle" to manage how many backup files I want to keep in the Google Storage Bucket.
How to reproduce it (as minimally and precisely as possible):
<~--
This could be something like:
values.yaml (only put values which differ from the defaults)
-->
Anything else we need to know:
The text was updated successfully, but these errors were encountered: