CrashLoopBackOff nextcloud-team-nextcloud-db

NextCloud not working anymore. I found out that this is caused by mariadb.

kubectl logs -f nextcloud-team-nextcloud-db-76c6ccb6fc-jgnhs
2022-09-01 10:30:31+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.9.2+maria~ubu2204 started.
2022-09-01 10:30:31+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2022-09-01 10:30:31+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.9.2+maria~ubu2204 started.
2022-09-01 10:30:31+00:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required
2022-09-01 10:30:31+00:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade) required, but skipped due to $MARIADB_AUTO_UPGRADE setting
2022-09-01 10:30:31 0 [Note] mariadbd (server 10.9.2-MariaDB-1:10.9.2+maria~ubu2204) starting as process 1 ...
bla bla
2022-09-01 10:30:31 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.5.4.

How can I fix this?
I tried already to edit deploy_database.yaml (image: mariadb:10.5) but that alone did not help.

I have to use a helm command to bring this modified configuration to run?

Sorry - no idea of kubenet

Start by reading deploy_database.yaml and the MariaDB image/version settings, then inspect the cited kubectl logs and Helm deployment configuration. Determine the supported recovery or upgrade path for the crash-looping database and document a reproducible fix; no test is named in the issue.

Written by the indexing model from the issue text.