For the French version please check this article: Impact du changement de catalogue Bitnami sur AFAH

1. Synthesis of the situation

By the 28^th of September, Bitnami announced a change in their policy to distribute their Docker image in their repository.

Upcoming change in Bitnami repository

Bitnami is one of the largest and most renowned image providers on the web. With this change, only the latest image will be kept inside their usual Bitnami repository, so it won’t be possible to find an image with a specific version tag anymore from there.

2. Impact on AFAH

AFAH is not directly impacted by this change, as we are not using these images when building the product image we are supplying to our customers.

Nevertheless, we have traditionally recommended the usage of the Bitnami image for external services we are not providing as part of our Docker image:

· MongoDB for Studio

· PHPFPM for Model

· NGNIX for Model

These images are just a recommendation from Axway and are embedded as such in our Helm chart; it’s still the customer’s final responsibility to run these services and ensure they stay available.

After September 28, if you run AFAH helm chart as is, the helm chart will fail due to referencing a specific version number that is no longer available in the Bitnami repository.

3. Recommended remediation

For our Axway cloud customers, we are managing the situation closely, and all images are stored in our internal Cloud Repository, so no impact is anticipated.

For on-premises customers, we recommend 2 actions:

· Make sure that your Docker or Kubernetes deployment points toward your internal repository, where you have stored the images

· Switch to the Legacy Bitnami repository that still proposes images with older tags

In update 11, AFAH will modify all its Helm charts to point toward this legacy repository.