MariaDB 10.5 no longer working on helm chart.

[Donkeyotee]

Name and Version

bitnami/mariadb-galera

What architecture are you using?

None

What steps will reproduce the bug?

In Kubernetes

• Client Version: v1.28.2
• Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
• Server Version: v1.28.6

Using the latest Helm chart.

# Please edit the object below. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this file will be
# reopened with the relevant failures.
#
apiVersion: apps/v1
kind: StatefulSet
metadata:
  annotations:
    meta.helm.sh/release-name: 
    meta.helm.sh/release-namespace:
  creationTimestamp: "2024-07-10T19:30:01Z"
  generation: 1
  labels:
    app.kubernetes.io/instance: mirth-mariadb
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: mariadb-galera
    app.kubernetes.io/version: 11.3.2
    helm.sh/chart: mariadb-galera-13.2.7
  name: mirth-mariadb-mariadb-galera

If you try to use MySQL 10.5 it will fail because wresp_mode has been added as a default configuration.

This mysql config was introduced in 10.6 meaning the 10.5 MySQL LTS will not work with this helm chart anymore.

This is not a huge issue but does put me specifically in a bit of a pickle as I must use 10.5 for a bit longer.

Are you using any custom parameters or values?

No

What is the expected behavior?

10.5 would be able to run on this provided HELM chart.

What do you see instead?

Pod crashback loop due to not understanding that newly introduced variable.

Additional information

Nothing really just wanted to let you know and hope you may be able to remove it and allow it as an optional setting. Thanks for maintaining this HELM

[carrodher]

Each Helm chart functions as a package that is tested with a specific combination of source code (Helm chart templates) and container images. Deviating from this tested combination may lead to unpredictable results, which we cannot guarantee.

Replacing the container images to use a different version it is not recommended as it has not been tested, it could or could not work, but it is not something we provide support for.

[Donkeyotee]

Thanks for the information I have noted this. Have a good day.

On Wed, Jul 10, 2024 at 11:59 PM Carlos Rodríguez Hernández < @.***> wrote:

Each Helm chart functions as a package that is tested with a specific combination of source code (Helm chart templates) and container images. Deviating from this tested combination may lead to unpredictable results, which we cannot guarantee.

Replacing the container images to use a different version it is not recommended as it has not been tested, it could or could not work, but it is not something we provide support for.

— Reply to this email directly, view it on GitHub https://github.com/bitnami/charts/issues/27889#issuecomment-2222097601, or unsubscribe https://github.com/notifications/unsubscribe-auth/BAD5MOIMODZRFDNJMWN5SE3ZLYNK3AVCNFSM6AAAAABKVV2FIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRSGA4TONRQGE . You are receiving this because you authored the thread.Message ID: @.***>

[github-actions[bot]]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions[bot]]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.