Should we use one Azure Container Registry (ACR) for Non Production and Production?

Sachin Vettiyattil-FT 41 Reputation points

A question that we have - should we have one Azure Container Registry (ACR) serving the non production (development) and production. At present in production we plan to have a different ACR to which the images will be imported from the development.

But the question is - what is the recommended way? If we treat ACR as an artifactory, then one is enough. After all, we have only one instance of Azure Artifacts (with several different feeds) where we push our nuget packages. Both nuget packages and docker images are build artifacts, so there is an argument that if we have just one nuget artifactory, why have multiple ACRs?

Azure Container Registry
Azure Container Registry
An Azure service that provides a registry of Docker and Open Container Initiative images.
428 questions
Azure ISV (Independent Software Vendors) and Startups
Azure ISV (Independent Software Vendors) and Startups
Azure: A cloud computing platform and infrastructure for building, deploying and managing applications and services through a worldwide network of Microsoft-managed datacenters.ISV (Independent Software Vendors) and Startups: A Microsoft program that helps customers adopt Microsoft Cloud solutions and drive user adoption.
91 questions
0 comments No comments
{count} votes

Accepted answer
  1. JimmySalian-2011 42,066 Reputation points

    Hi Sachin,

    I will recommend you to refer to the architecture articles and take a base decision on your requirements .hybrid-containers

    Also follow the best practices information to make a design decision based on this - container-registry-best-practices

    Hope this helps.

    Please Accept the answer if the information helped you. This will help us and others in the community as well.

    0 comments No comments

0 additional answers

Sort by: Most helpful