mirror of
https://github.com/bitnami/charts.git
synced 2026-04-02 07:17:26 +08:00
[bitnami/seaweedfs] chore!: ⬆️ 💥 Bump MariaDB subchart to 20 (#30358)
* [bitnami/seaweedfs] chore!: ⬆️ 💥 Bump MariaDB subchart to 20 Signed-off-by: Javier J. Salmerón García <javier.salmeron@broadcom.com> * Update CHANGELOG.md Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> * chore: 🔥 Remove deprecated value Signed-off-by: Javier J. Salmerón García <javier.salmeron@broadcom.com> * Update CHANGELOG.md Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> * Update README.md with readme-generator-for-helm Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> --------- Signed-off-by: Javier J. Salmerón García <javier.salmeron@broadcom.com> Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> Co-authored-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
committed by
GitHub
parent
2324895033
commit
1d471fd9fa
@@ -1,8 +1,12 @@
|
||||
# Changelog
|
||||
|
||||
## 4.0.0 (2024-11-12)
|
||||
|
||||
* [bitnami/seaweedfs] chore!: :arrow_up: :boom: Bump MariaDB subchart to 20 ([#30358](https://github.com/bitnami/charts/pull/30358))
|
||||
|
||||
## 3.2.0 (2024-11-08)
|
||||
|
||||
* [bitnami/seaweedfs] Support configuring volume size limit on Master ([#30315](https://github.com/bitnami/charts/pull/30315))
|
||||
* [bitnami/seaweedfs] Support configuring volume size limit on Master (#30315) ([0dc86e0](https://github.com/bitnami/charts/commit/0dc86e09237ecaabf57d6c7b66d53dd461256e69)), closes [#30315](https://github.com/bitnami/charts/issues/30315)
|
||||
|
||||
## 3.1.0 (2024-11-07)
|
||||
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
dependencies:
|
||||
- name: mariadb
|
||||
repository: oci://registry-1.docker.io/bitnamicharts
|
||||
version: 19.1.2
|
||||
version: 20.0.0
|
||||
- name: postgresql
|
||||
repository: oci://registry-1.docker.io/bitnamicharts
|
||||
version: 16.1.2
|
||||
- name: common
|
||||
repository: oci://registry-1.docker.io/bitnamicharts
|
||||
version: 2.27.0
|
||||
digest: sha256:52f6529af58fbffd7c62e51615352e0534218c47ced98183dc9b7cfc01f432f4
|
||||
generated: "2024-11-07T09:43:50.280362706Z"
|
||||
digest: sha256:39bd4de2a9cd5ed6c24340ef5d49c6ded7c905b0435f22dc0dfc5c6614e08716
|
||||
generated: "2024-11-08T16:26:54.275710607+01:00"
|
||||
|
||||
@@ -21,7 +21,7 @@ dependencies:
|
||||
repository: oci://registry-1.docker.io/bitnamicharts
|
||||
tags:
|
||||
- seaweedfs-database
|
||||
version: 19.x.x
|
||||
version: 20.x.x
|
||||
- condition: postgresql.enabled
|
||||
name: postgresql
|
||||
repository: oci://registry-1.docker.io/bitnamicharts
|
||||
@@ -50,4 +50,4 @@ name: seaweedfs
|
||||
sources:
|
||||
- https://github.com/bitnami/charts/tree/main/bitnami/seawwedfs
|
||||
- https://github.com/bitnami/containers/tree/main/bitnami/seaweedfs
|
||||
version: 3.2.0
|
||||
version: 4.0.0
|
||||
|
||||
@@ -214,7 +214,6 @@ If you encounter errors when working with persistent volumes, refer to our [trou
|
||||
| `global.imageRegistry` | Global Docker image registry | `""` |
|
||||
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` |
|
||||
| `global.defaultStorageClass` | Global default StorageClass for Persistent Volume(s) | `""` |
|
||||
| `global.storageClass` | DEPRECATED: use global.defaultStorageClass instead | `""` |
|
||||
| `global.compatibility.openshift.adaptSecurityContext` | Adapt the securityContext sections of the deployment to make them compatible with Openshift restricted-v2 SCC: remove runAsUser, runAsGroup and fsGroup and let the platform use their allowed default IDs. Possible values: auto (apply if the detected running cluster is Openshift), force (perform the adaptation always), disabled (do not perform adaptation) | `auto` |
|
||||
|
||||
### Common parameters
|
||||
@@ -1161,6 +1160,16 @@ helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/seawe
|
||||
|
||||
## Upgrading
|
||||
|
||||
### To 4.0.0
|
||||
|
||||
This major bump updates the MariaDB subchart to version 20.0.0. This subchart updates the StatefulSet objects `serviceName` to use a headless service, as the current non-headless service attached to it was not providing DNS entries. This will cause an upgrade issue because it changes "immutable fields". To workaround it, delete the StatefulSet objects as follows (replace the RELEASE_NAME placeholder):
|
||||
|
||||
```shell
|
||||
kubectl delete sts RELEASE_NAME-mariadb --cascade=false
|
||||
```
|
||||
|
||||
Then execute `helm upgrade` as usual.
|
||||
|
||||
### To 3.0.0
|
||||
|
||||
This major updates the PostgreSQL subchart to its newest major, 16.0.0, which uses PostgreSQL 17.x. Follow the [official instructions](https://www.postgresql.org/docs/17/upgrading.html) to upgrade to 17.x.
|
||||
|
||||
@@ -10,7 +10,6 @@
|
||||
## @param global.imageRegistry Global Docker image registry
|
||||
## @param global.imagePullSecrets Global Docker registry secret names as an array
|
||||
## @param global.defaultStorageClass Global default StorageClass for Persistent Volume(s)
|
||||
## @param global.storageClass DEPRECATED: use global.defaultStorageClass instead
|
||||
##
|
||||
global:
|
||||
imageRegistry: ""
|
||||
@@ -20,7 +19,6 @@ global:
|
||||
##
|
||||
imagePullSecrets: []
|
||||
defaultStorageClass: ""
|
||||
storageClass: ""
|
||||
## Compatibility adaptations for Kubernetes platforms
|
||||
##
|
||||
compatibility:
|
||||
|
||||
Reference in New Issue
Block a user