Skip to content

[bitnami/harbor] Add support for registry storage upload purging setting #33587

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.

Sign up for GitHub

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
+33 −3
Open

[bitnami/harbor] Add support for registry storage upload purging setting #33587

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f8b0868
[bitnami/harbor] feat(registry): add support for storage upload purging
keviiin38 May 9, 2025
5b02312
Update CHANGELOG.md
bitnami-bot May 9, 2025
05100c5
Merge branch 'main' into main
carrodher May 9, 2025
8b52c10
Update CHANGELOG.md
bitnami-bot May 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions bitnami/harbor/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,17 @@
# Changelog

## 26.0.0 (2025-05-08)
## 26.1.0 (2025-05-09)

* [bitnami/harbor] feat!: :arrow_up: :boom: Bump Redis(R) to 8.0 ([#33502](https://github.com/bitnami/charts/pull/33502))
* [bitnami/harbor] Add support for registry storage upload purging setting ([#33587](https://github.com/bitnami/charts/pull/33587))

## <small>26.0.1 (2025-05-09)</small>

* [bitnami/harbor] :zap: :arrow_up: Update dependency references (#33596) ([0259db0](https://github.com/bitnami/charts/commit/0259db0c2f6d7eae28777399bf075fbb0bcb6b65)), closes [#33596](https://github.com/bitnami/charts/issues/33596)

## 26.0.0 (2025-05-09)

* [bitnami/harbor] feat!: :arrow_up: :boom: Bump Redis(R) to 8.0 (#33502) ([1fe91e0](https://github.com/bitnami/charts/commit/1fe91e0de5f7f343c31ff8bd8ac44ace87253207)), closes [#33502](https://github.com/bitnami/charts/issues/33502)
* [bitnami/kubeapps] Deprecation followup (#33579) ([77e312c](https://github.com/bitnami/charts/commit/77e312c1772d4d7c4dc5d3ac0e80f4e452e3a062)), closes [#33579](https://github.com/bitnami/charts/issues/33579)

## <small>25.0.2 (2025-05-08)</small>

Expand Down
2 changes: 1 addition & 1 deletion bitnami/harbor/Chart.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,4 +56,4 @@ maintainers:
name: harbor
sources:
- https://github.com/bitnami/charts/tree/main/bitnami/harbor
version: 26.0.1
version: 26.1.0
4 changes: 4 additions & 0 deletions bitnami/harbor/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -300,6 +300,10 @@ You can enable this initContainer by setting `volumePermissions.enabled` to `tru
| `persistence.persistentVolumeClaim.trivy.selector` | Selector to match an existing Persistent Volume | `{}` |
| `persistence.imageChartStorage.caBundleSecret` | Specify the `caBundleSecret` if the storage service uses a self-signed certificate. The secret must contain keys named `ca.crt` which will be injected into the trust store of registry's containers. | `""` |
| `persistence.imageChartStorage.disableredirect` | The configuration for managing redirects from content backends. For backends which do not supported it (such as using MinIO&reg; for `s3` storage type), please set it to `true` to disable redirects. Refer to the [guide](https://github.com/docker/distribution/blob/master/docs/configuration.md#redirect) for more information about the detail | `false` |
| `persistence.imageChartStorage.uploadpurging.enabled` | Maintenance upload purging setting: Set to `true` to enable upload purging. (Defaults to `false` for backward compatibility) | `false` |
| `persistence.imageChartStorage.uploadpurging.age` | Maintenance upload purging setting: Upload directories which are older than this age will be deleted | `168h` |
| `persistence.imageChartStorage.uploadpurging.interval` | Maintenance upload purging setting: The interval between upload directory purging | `24h` |
| `persistence.imageChartStorage.uploadpurging.dryrun` | Maintenance upload purging setting: Set to `true` to obtain a summary of what directories will be deleted | `false` |
| `persistence.imageChartStorage.type` | The type of storage for images and charts: `filesystem`, `azure`, `gcs`, `s3`, `swift` or `oss`. The type must be `filesystem` if you want to use persistent volumes for registry. Refer to the [guide](https://github.com/docker/distribution/blob/master/docs/configuration.md#storage) for more information about the detail | `filesystem` |
| `persistence.imageChartStorage.filesystem.rootdirectory` | Filesystem storage type setting: Storage root directory | `/storage` |
| `persistence.imageChartStorage.filesystem.maxthreads` | Filesystem storage type setting: Maximum threads directory | `""` |
Expand Down
7 changes: 7 additions & 0 deletions bitnami/harbor/templates/registry/registry-cm.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,7 +157,14 @@ data:
layerinfo: redis
maintenance:
uploadpurging:
{{- if .Values.persistence.imageChartStorage.uploadpurging.enabled }}
enabled: true
age: {{ .Values.persistence.imageChartStorage.uploadpurging.age }}
interval: {{ .Values.persistence.imageChartStorage.uploadpurging.interval }}
dryrun: {{ .Values.persistence.imageChartStorage.uploadpurging.dryrun }}
{{- else }}
enabled: false
{{- end }}
delete:
enabled: true
redirect:
Expand Down
10 changes: 10 additions & 0 deletions bitnami/harbor/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -389,6 +389,16 @@ persistence:
## @param persistence.imageChartStorage.disableredirect The configuration for managing redirects from content backends. For backends which do not supported it (such as using MinIO&reg; for `s3` storage type), please set it to `true` to disable redirects. Refer to the [guide](https://github.com/docker/distribution/blob/master/docs/configuration.md#redirect) for more information about the detail
##
disableredirect: false
## Upload purging is a background process that periodically removes orphaned files from the upload directories of the registry
## @param persistence.imageChartStorage.uploadpurging.enabled Maintenance upload purging setting: Set to `true` to enable upload purging. (Defaults to `false` for backward compatibility)
## @param persistence.imageChartStorage.uploadpurging.age Maintenance upload purging setting: Upload directories which are older than this age will be deleted
## @param persistence.imageChartStorage.uploadpurging.interval Maintenance upload purging setting: The interval between upload directory purging
## @param persistence.imageChartStorage.uploadpurging.dryrun Maintenance upload purging setting: Set to `true` to obtain a summary of what directories will be deleted
uploadpurging:
enabled: false
age: 168h # 1 week
interval: 24h
dryrun: false
## @param persistence.imageChartStorage.type The type of storage for images and charts: `filesystem`, `azure`, `gcs`, `s3`, `swift` or `oss`. The type must be `filesystem` if you want to use persistent volumes for registry. Refer to the [guide](https://github.com/docker/distribution/blob/master/docs/configuration.md#storage) for more information about the detail
##
type: filesystem
Expand Down
Loading