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

* [bitnami/ejbca] 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>

---------

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:
Javier J. Salmerón García
2024-11-12 15:26:55 +01:00
committed by GitHub
co-authored by Bitnami Containers
parent 1d471fd9fa
commit 2a3ac05227
5 changed files with 24 additions and 11 deletions
+8 -2
View File
@@ -1,8 +1,14 @@
# Changelog
## 15.0.8 (2024-11-08)
## 16.0.0 (2024-11-12)
* [bitnami/ejbca] Unify seLinuxOptions default value ([#30345](https://github.com/bitnami/charts/pull/30345))
* [bitnami/ejbca] chore!: :arrow_up: :boom: Bump MariaDB subchart to 20 ([#30353](https://github.com/bitnami/charts/pull/30353))
## <small>15.0.8 (2024-11-08)</small>
* [bitnami/*] Remove wrong comment about imagePullPolicy (#30107) ([a51f9e4](https://github.com/bitnami/charts/commit/a51f9e4bb0fbf77199512d35de7ac8abe055d026)), closes [#30107](https://github.com/bitnami/charts/issues/30107)
* [bitnami/ejbca] Unify seLinuxOptions default value (#30345) ([ab673bb](https://github.com/bitnami/charts/commit/ab673bba8586f42cf8ba3829cb36c65b7ecb6123)), closes [#30345](https://github.com/bitnami/charts/issues/30345)
* Update documentation links to techdocs.broadcom.com (#29931) ([f0d9ad7](https://github.com/bitnami/charts/commit/f0d9ad78f39f633d275fc576d32eae78ded4d0b8)), closes [#29931](https://github.com/bitnami/charts/issues/29931)
## <small>15.0.7 (2024-10-07)</small>
+4 -4
View File
@@ -1,9 +1,9 @@
dependencies:
- name: mariadb
repository: oci://registry-1.docker.io/bitnamicharts
version: 19.0.7
version: 20.0.0
- name: common
repository: oci://registry-1.docker.io/bitnamicharts
version: 2.24.0
digest: sha256:f7bd48410fc5dfe1817c11c147fc9299eccd46478475e6c73bf38e9504498ded
generated: "2024-10-07T09:51:50.516786827Z"
version: 2.27.0
digest: sha256:f2778c936bac0bad137df5b1d51eb8d7591bdc7749db7edb2c78a5384fa3846f
generated: "2024-11-08T16:11:38.448357185+01:00"
+2 -2
View File
@@ -15,7 +15,7 @@ dependencies:
repository: oci://registry-1.docker.io/bitnamicharts
tags:
- ejbca-database
version: 19.x.x
version: 20.x.x
- name: common
repository: oci://registry-1.docker.io/bitnamicharts
tags:
@@ -35,4 +35,4 @@ maintainers:
name: ejbca
sources:
- https://github.com/bitnami/charts/tree/main/bitnami/ejbca
version: 15.0.8
version: 16.0.0
+10 -1
View File
@@ -148,7 +148,6 @@ Persistent Volume Claims are used to keep the data across deployments. This is k
| `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
@@ -369,6 +368,16 @@ Find more information about how to deal with common errors related to Bitnami's
## Upgrading
### To 16.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 15.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
View File
@@ -9,7 +9,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: ""
@@ -19,7 +18,6 @@ global:
##
imagePullSecrets: []
defaultStorageClass: ""
storageClass: ""
## Compatibility adaptations for Kubernetes platforms
##
compatibility: