mirror of
https://github.com/bitnami/charts.git
synced 2026-08-10 14:15:55 +08:00
[bitnami/minio] fix: chown in the volume-permissions will only work if the CHOWN capability is added (#34311)
* fix: chown in the volume-permissions will only work if the CHOWN capability is added Signed-off-by: Jörg Markert <joerg.markert@gmail.com> * Update CHANGELOG.md Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com> * Update README.md with readme-generator-for-helm Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com> * Update CHANGELOG.md Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com> --------- Signed-off-by: Jörg Markert <joerg.markert@gmail.com> Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com> Co-authored-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
@@ -1,8 +1,12 @@
|
||||
# Changelog
|
||||
|
||||
## 17.0.3 (2025-06-06)
|
||||
## 17.0.4 (2025-06-11)
|
||||
|
||||
* [bitnami/minio] :zap: :arrow_up: Update dependency references ([#34195](https://github.com/bitnami/charts/pull/34195))
|
||||
* [bitnami/minio] fix: chown in the volume-permissions will only work if the CHOWN capability is added ([#34311](https://github.com/bitnami/charts/pull/34311))
|
||||
|
||||
## <small>17.0.3 (2025-06-06)</small>
|
||||
|
||||
* [bitnami/minio] :zap: :arrow_up: Update dependency references (#34195) ([303327d](https://github.com/bitnami/charts/commit/303327d49a16222d82bf2fca322794990fc469f9)), closes [#34195](https://github.com/bitnami/charts/issues/34195)
|
||||
|
||||
## <small>17.0.2 (2025-06-04)</small>
|
||||
|
||||
|
||||
@@ -39,4 +39,4 @@ maintainers:
|
||||
name: minio
|
||||
sources:
|
||||
- https://github.com/bitnami/charts/tree/main/bitnami/minio
|
||||
version: 17.0.3
|
||||
version: 17.0.4
|
||||
|
||||
@@ -383,7 +383,7 @@ You can enable this initContainer by setting `volumePermissions.enabled` to `tru
|
||||
| `defaultInitContainers.volumePermissions.containerSecurityContext.runAsUser` | Set runAsUser in "volume-permissions" init-containers' Security Context | `0` |
|
||||
| `defaultInitContainers.volumePermissions.containerSecurityContext.privileged` | Set privileged in "volume-permissions" init-containers' Security Context | `false` |
|
||||
| `defaultInitContainers.volumePermissions.containerSecurityContext.allowPrivilegeEscalation` | Set allowPrivilegeEscalation in "volume-permissions" init-containers' Security Context | `false` |
|
||||
| `defaultInitContainers.volumePermissions.containerSecurityContext.capabilities.add` | List of capabilities to be added in "volume-permissions" init-containers | `[]` |
|
||||
| `defaultInitContainers.volumePermissions.containerSecurityContext.capabilities.add` | List of capabilities to be added in "volume-permissions" init-containers | `["CHOWN"]` |
|
||||
| `defaultInitContainers.volumePermissions.containerSecurityContext.capabilities.drop` | List of capabilities to be dropped in "volume-permissions" init-containers | `["ALL"]` |
|
||||
| `defaultInitContainers.volumePermissions.containerSecurityContext.seccompProfile.type` | Set seccomp profile in "volume-permissions" init-containers | `RuntimeDefault` |
|
||||
| `defaultInitContainers.volumePermissions.resourcesPreset` | Set MinIO® "volume-permissions" init container resources according to one common preset (allowed values: none, nano, small, medium, large, xlarge, 2xlarge). This is ignored if defaultInitContainers.volumePermissions.resources is set (defaultInitContainers.volumePermissions.resources is recommended for production). | `nano` |
|
||||
|
||||
@@ -540,7 +540,7 @@ defaultInitContainers:
|
||||
privileged: false
|
||||
allowPrivilegeEscalation: false
|
||||
capabilities:
|
||||
add: []
|
||||
add: ["CHOWN"]
|
||||
drop: ["ALL"]
|
||||
seccompProfile:
|
||||
type: "RuntimeDefault"
|
||||
|
||||
Reference in New Issue
Block a user