Bitnami/charts
2
0
Fork 0
mirror of https://github.com/bitnami/charts.git synced 2026-03-05 14:57:31 +08:00
Code Issues Packages Projects Releases Wiki Activity

[bitnami/wordpress] chore!: ⬆️ 💥 Bump MariaDB subchart to 20 (#30360)

Browse Source
This commit is contained in:
Javier J. Salmerón García
2024-11-12 12:54:45 +01:00
committed by GitHub
parent 21e98a53e0
commit f3ecd60118
5 changed files with 21 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
bitnami/wordpress/CHANGELOG.md
View File

@@ -1,8 +1,12 @@
# Changelog
## 23.1.29 (2024-11-10)
## 24.0.0 (2024-11-12)
* [bitnami/wordpress] Release 23.1.29 ([#30310](https://github.com/bitnami/charts/pull/30310))
* [bitnami/wordpress] chore!: :arrow_up: :boom: Bump MariaDB subchart to 20 ([#30360](https://github.com/bitnami/charts/pull/30360))
## <small>23.1.29 (2024-11-11)</small>
* [bitnami/wordpress] Release 23.1.29 (#30310) ([bab05f7](https://github.com/bitnami/charts/commit/bab05f726f165eb2c21946b15747c8ff6f35d446)), closes [#30310](https://github.com/bitnami/charts/issues/30310)
## <small>23.1.28 (2024-11-06)</small>

6
bitnami/wordpress/Chart.lock
View File

@@ -4,9 +4,9 @@ dependencies:
version: 7.5.2
- name: mariadb
repository: oci://registry-1.docker.io/bitnamicharts
version: 19.1.2
version: 20.0.0
- name: common
repository: oci://registry-1.docker.io/bitnamicharts
version: 2.27.0
digest: sha256:f033c21f98cfedcc98f2cae559a44ce12d6f7f9b77a1ddb09696b1265381887e
generated: "2024-11-07T22:41:53.465196992Z"
digest: sha256:57e60f96e250d5da0132529d676a700c0e86f635ec6cb162f6f34eb0a5376665
generated: "2024-11-08T16:30:47.3649782+01:00"

4
bitnami/wordpress/Chart.yaml
View File

@@ -21,7 +21,7 @@ dependencies:
- condition: mariadb.enabled
name: mariadb
repository: oci://registry-1.docker.io/bitnamicharts
version: 19.x.x
version: 20.x.x
- name: common
repository: oci://registry-1.docker.io/bitnamicharts
tags:
@@ -44,4 +44,4 @@ maintainers:
name: wordpress
sources:
- https://github.com/bitnami/charts/tree/main/bitnami/wordpress
version: 23.1.29
version: 24.0.0

11
bitnami/wordpress/README.md
View File

@@ -247,7 +247,6 @@ As an alternative, use one of the preset configurations for pod affinity, pod an
| `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
@@ -636,6 +635,16 @@ To enable the new features, it is not possible to do it by upgrading an existing
## Upgrading
### To 24.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 23.0.0
This major release bumps the MariaDB version to 11.4. Follow the [upstream instructions](https://mariadb.com/kb/en/upgrading-from-mariadb-11-3-to-mariadb-11-4/) for upgrading from MariaDB 11.3 to 11.4. No major issues are expected during the upgrade.

2
bitnami/wordpress/values.yaml
View File

@@ -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: