Missing tag on docker image

[etiennnr]

Name and Version

rabbitmq-cluster-operator any

What steps will reproduce the bug?

I noticed that the docker image docker.io/bitnami/rmq-messaging-topology-operator doesn't have any tags, which made my last update fail.

So I cannot pull it unless using the "real" upsteam image ghcr.io/rabbitmq/messaging-topology-operator:1.17.4.

Ideally, I would like the use the default image tag based in the chart's version that I'm using. However, your tagging doesn't follow the same pattern so I cannot "just" change the image reference.

So, is it on purpose that the image from the bitnami repo doesn't have any tags ?

Are you using any custom parameters or values?

No response

What is the expected behavior?

No response

What do you see instead?

No tag on the docker image

Additional information

No response

[opb]

I'm not trying to use the chart/image that you're using, but I'm seeing the same thign with the postgres image. The bitnami postgres chart version I'm using is trying to pull bitnami/postgresql:16.4.0-debian-12-r9, but the only tag which seems to be available is latest. This was previously working, and I found it broken today. not sure when it broke.

[SoroushTaheri]

AFAIK, this seems to be related to the planned changes to Bitnami catalog (bitnami/containers#83267 (comment))

Community catalog

• Disable images generation for Debian-based images and gradually move existing ones to a Bitnami Legacy repository.
• A focused set of more hardened, more secure images. These free images are intended for development and are only available on the “latest” tag. You can find them at https://hub.docker.com/u/bitnamisecure.
• Helm charts and container images' open-source code will continue to be maintained up-to-date and accessible on GitHub under the Apache 2 license.

Legacy repository migration

• All existing container images, including older or versioned tags (e.g., 2.50.0, 10.6), will be moved from the public catalog (docker.io/bitnami) to the Bitnami Legacy repository (docker.io/bitnamilegacy). This legacy catalog will receive no further updates or support and should only be used for temporary migration purposes.
• Exception: Images based on distros deprecated from the Bitnami catalog more than 3 years ago (tags: debian-8, debian-9, debian-10, centos-7, ol-7) will not be copied.
• Suppose your deployed Helm chart is failing to pull images from docker.io/bitnami. In that case, you can resolve this by subscribing to Bitnami Secure Images, ensuring that the Helm charts receive continued support and security updates. As a temporary workaround, you can upgrade to the same version and update the repository parameter for each container image to the Bitnami Legacy repository.

[carrodher]

With the changes announced at bitnami/containers#83267, the container images were removed from docker.io/bitnami and moved to docker.io/bitnamilegacy, where they will no longer receive updates. To continue getting new, hardened image versions, a Bitnami Secure Images subscription is required.

A small subset of container images and Helm charts will be maintained as part of a BSI trial. Here you can view the list of applications included in the trial.

Please take a look at the pinned issue linked above for full details.

[opb]

Thanks to both responders for taking the time to do so. I found that overriding image.repository and setting it to bitnamilegacy/postgresql fixed things for me. I will work out an upgrade path.

Thanks again

EDIT: autocorrect on repo name

[etiennnr]

Indeed, looks like now have to use the "real" upstream image instead of the default one from the chart... I get using bitnami's secure images is under a subscription, but this decision make all existing helm charts fails to install...

@carrodher Is there a plan to update the default values if the helm charts in order to at lease use working images ? Or is this also no going to get updated anymore?

[SoroushTaheri]

Indeed, looks like now have to use the "real" upstream image instead of the default one from the chart... I get using bitnami's secure images is under a subscription, but this decision make all existing helm charts fails to install...

My concern here is whether the original ("real") images are guaranteed to remain fully compatible with the chart’s values, environment variables, and configuration assumptions.

Am I misunderstanding this?

[etiennnr]

Indeed, looks like now have to use the "real" upstream image instead of the default one from the chart... I get using bitnami's secure images is under a subscription, but this decision make all existing helm charts fails to install...

My concern here is whether the original ("real") images are guaranteed to remain fully compatible with the chart’s values, environment variables, and configuration assumptions.

Am I misunderstanding this?

Indeed, I have exactly the same concern!

[github-actions]

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.

[etiennnr]

@carrodher, can you please answer #36459 (comment) ?