Upgrade RabbitMQ Subchart (and Metacat PostgreSQL)

[artntek]

The Released version 1.0.0 of the metacat helm chart has dependencies:

1. Postgres Bitnami chart:

    version: 11.9.13    # postgres version 14.5.0 is deployed by chart version 11.9.13

2. dataone-indexer-1.0.0 subchart, which has a dependency on RabbitMQ Bitnami chart:

    version: 10.1.14    # rabbitmq version 3.10.5 is deployed by chart version 10.1.14

Problem

HOWEVER, if we upgrade the RabbitMQ Bitnami sub-sub-chart:

    version: 14.1.0     # rabbitmq version 3.13.1 is deployed by chart version 14.1.0

...then this breaks the postgres subchart, because of a conflict.

Solution

to upgrade postgres to any bitnami chart version >12.9 (which is postgres 15+) - so before we do that, we need to create an upgrade path for postgres 14 -> 15, and ideally 15 -> 16, so we can upgrade to the latest - e.g:

1. Postgres Bitnami chart:

    version: 15.2.9    # postgres version 16.2.0 is deployed by chart version 15.2.9

After this is done (see Metacat Issue #1748: "Automate k8s Postgresql Upgrades after 3.0.0 release"), we can then upgrade RabbitMQ without incompatibility issues.

[artntek]

In addition to the regular benefits of upgrading, this will also allow rmq (and therefore metacat) to be deployed on mac silicon (docker- or rancher desktop)