[bitnami/harbor] Add support for registry storage upload purging setting #33587
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.
Description of the change
Add the option to configure of the uploadpurging setting in the registry
storage.maintenance
section.Benefits
With this change, the registry could clean the
_uploads
folders if enabled, which could save a lot of space on the storage backend.Possible drawbacks
Currently, the value is hardcoded to
enabled: false
, in order to prevent massive deletes on the storage backend, the defaultenabled: false
has been kept in the values.yaml file.As opposed to the default values of distribution/distribution which is
enabled: true
.Applicable issues
Additional information
Checklist
Chart.yaml
according to semver. This is not necessary when the changes only affect README.md files.README.md
using readme-generator-for-helm