Docker deployments: healthplatformregistry.azurecr.io is unreliable

[elgib]

Summary:
When using docker container deployments, the recommended registry healthplatformregistry.azurecr.io/r4_fhir-server is unreliable. Is there another option suitable for Azure container app deployments in production environments?

Details:
We have deployed Azure FHIR servers for development, testing, and production environments using the recommended
templates for docker container deployments with the registry name "healthplatformregistry.azurecr.io". We also specify an image tag in the deployment center:

We occasionally encounter errors where the FHIR servers (spontaneously) attempt to redeploy and the tagged docker images are not available, resulting in downtime:

In the past we have been able to resolve these issues by switching to a different tag, but none of the versions that we've tried are available on the healthplatformregistry.azurecr.io/r4_fhir-server registry at the moment.

We found the R4 FHIR Server images in the Microsoft Artifact Registry and have switched to using this registry instead, which is working.

Questions:

• What happened to the healthplatformregistry.azurecr.io/r4_fhir-server registry, and should we avoid using it in future?
• Is the R4 FHIR Server Microsoft Artifact Registry likely to be more reliable for our production environment, or do we need to investigate other deployment strategies to minimize the risk of downtime?
• Are we overlooking some obvious way to prevent the unplanned redeployments on the Azure container apps?