[bitnami/mariadb-galera] Major version. Adapt Chart to apiVersion: v2 (#4275)

* [bitnami/mariadb-galera] Major version. Adapt Chart to apiVersion: v2

* [bitnami/mariadb-galera] Update components versions

Signed-off-by: Bitnami Containers <containers@bitnami.com>

Co-authored-by: Bitnami Containers <containers@bitnami.com>
This commit is contained in:
Carlos Rodríguez Hernández
2020-11-11 00:48:45 +01:00
committed by GitHub
parent dcefb9d60d
commit 950c3efe7d
4 changed files with 37 additions and 16 deletions

View File

@@ -1,8 +1,11 @@
apiVersion: v1
name: mariadb-galera
version: 4.4.6
annotations:
category: Database
apiVersion: v2
appVersion: 10.5.7
description: MariaDB Galera is a multi-master database cluster solution for synchronous replication and high availability.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/mariadb-galera
icon: https://bitnami.com/assets/stacks/mariadb-galera/img/mariadb-galera-stack-220x234.png
keywords:
- mariadb
- mysql
@@ -11,15 +14,12 @@ keywords:
- prometheus
- galera
- percona
home: https://github.com/bitnami/charts/tree/master/bitnami/mariadb-galera
icon: https://bitnami.com/assets/stacks/mariadb-galera/img/mariadb-galera-stack-220x234.png
maintainers:
- email: containers@bitnami.com
name: Bitnami
name: mariadb-galera
sources:
- https://github.com/bitnami/bitnami-docker-mariadb-galera
- https://github.com/prometheus/mysqld_exporter
- https://mariadb.org
maintainers:
- name: Bitnami
email: containers@bitnami.com
engine: gotpl
annotations:
category: Database
version: 5.0.0

View File

@@ -18,7 +18,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
## Prerequisites
- Kubernetes 1.10+
- Helm 2.12+ or Helm 3.0-beta3+
- Helm 3.0-beta3+
- PV provisioner support in the underlying infrastructure
## Installing the Chart
@@ -492,6 +492,27 @@ $ helm upgrade my-release bitnami/mariadb-galera \
| Note: you need to substitute the placeholders _[ROOT_PASSWORD]_, _[MARIADB_PASSWORD]_ and _[MARIABACKUP_PASSWORD]_ with the values obtained from instructions in the installation notes.
### To 5.0.0
[On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
**What changes were introduced in this major version?**
- Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
- The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
**Considerations when upgrading to this version**
- If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
- If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
- If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
**Useful links**
- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
- https://helm.sh/docs/topics/v2_v3_migration/
- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
### To 2.0.0
In this version the bootstraping was improved. Now it is possible to indicate a node where to bootstrap from, and force the parameter `safe_to_bootstrap`. This allows to handle situations where the cluster was not cleanly stopped. It should be safe to upgrade from v1 of the chart, but it is wise to create always a backup before performing operations where there is a risk of data loss.

View File

@@ -14,7 +14,7 @@
image:
registry: docker.io
repository: bitnami/mariadb-galera
tag: 10.5.7-debian-10-r0
tag: 10.5.7-debian-10-r7
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
@@ -547,7 +547,7 @@ metrics:
image:
registry: docker.io
repository: bitnami/mysqld-exporter
tag: 0.12.1-debian-10-r257
tag: 0.12.1-debian-10-r263
pullPolicy: IfNotPresent
## Optionally specify an array of imagePullSecrets.
## Secrets must be manually created in the namespace.

View File

@@ -14,7 +14,7 @@
image:
registry: docker.io
repository: bitnami/mariadb-galera
tag: 10.5.7-debian-10-r0
tag: 10.5.7-debian-10-r7
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -546,7 +546,7 @@ metrics:
image:
registry: docker.io
repository: bitnami/mysqld-exporter
tag: 0.12.1-debian-10-r257
tag: 0.12.1-debian-10-r263
pullPolicy: IfNotPresent
## Optionally specify an array of imagePullSecrets.
## Secrets must be manually created in the namespace.