Closed dirkmueller closed 2 months ago
@zackbradys the maintenance of the helm chart was handed over to the RMT team. I don't know the state of this change (whether it has been released already) @felixsch ?
thanks for the quick update @dirkmueller.
so is the helm chart no longer maintained/published from this repo?
rmt-mariadb is an alias for mariadb, so you are already getting the generic ones I would say
that is true, but if I'm running in the airgap, the helm chart will fail (by default), unless I pull those images separately, then move across the airgap, then deploy the helm chart. a lot of customers would already have the mariadb
images loaded into their airgapped environments.
if the images are the same as mariadb
, why alias/retag them? additionally, the helm chart is already using nginx
not an alias/retag of nginx
so to me it would make sense to have it for mariadb
as well?
that is true, but if I'm running in the airgap, the helm chart will fail (by default), unless I pull those images separately, then move across the airgap, then deploy the helm chart. a lot of customers would already have the
mariadb
images loaded into their airgapped environments.if the images are the same as
mariadb
, why alias/retag them? additionally, the helm chart is already usingnginx
not an alias/retag ofnginx
so to me it would make sense to have it formariadb
as well?
It is a transition. The intention was to go with mariadb
, but we need to convert all our users first. One of the identified ones is RMT, which as you can see is still working on ingesting the change.
so is the helm chart no longer maintained/published from this repo?
It has never been published from this repo, it used to be maintained here. I don't know whether that is still the case here or whether the new team has moved it elsewhere already. I'm trying to find it out.
is this planning on being merged? it would be really useful to use the generic images. @dirkmueller