As we are discussing planning of your transition and adoption to a cloud platform, the modernization of your current applications using container technology is major role of the discussions. In that there are various cloud service providers in place. For now, we have seen how to run the container on google cloud, now it’s time to think about what another vendor’s is and how to deploy our container in that. This is various reason, what is if your organization plan for multi-cloud or different environment/team required multiple cloud technologies. All won’t be same always, there may be different requirements too. For that will see new leading cloud service provider Microsoft Azure.
Microsoft Azure is one of the good place to run your containers. It has several offerings and developers can get help from the ecosystem to build their DevOps scenarios to deploy containers, using Microsoft Visual Studio, Windows Server, and Microsoft Azure. If you value consistency, having the same vendor to cover the development, hosting, and cloud solution is a vital point to be considered when planning your journey to the cloud. One of the first components that your company could start taking advantage of with Azure Cloud is the Registry. Azure has the Azure Container Registry (ACR) service, which is a private registry. It is a managed service, which means that your focus is what really matters: manage images in a private and secure registry taking advantage of Azure logging capabilities, RBAC (role based access control), replication, and high availability.
Create Azure Container Registry
To create the registry, Login to the portal, click on Create a Resource, and type container on the search box, select Container Registry from the list. In the initial page, an overview of the service that we are about to start the creation of will be displayed. Click on Create.
In the Create container registry we have two option, first one is the unique name that will be used by the container registry, and the second is the SKU, which could be Basic (supports 10GB storage), Standard (100GB storage) or Premium (500GB storage and geo-replication capabilities. There are some differences in download and upload bandwidth limits for the SKUs, as well number of webhooks.
SKU Description Basic A cost-optimized entry point for developers learning about Azure Container Registry. Basic registries have the same programmatic capabilities as Standard and Premium (Azure Active Directory authentication integration, image deletion, and web hooks), however, there are size and usage constraints. Standard The Standard registry offers the same capabilities as Basic, but with increased storage limits and image throughput. Standard registries should satisfy the needs of most production scenarios. Premium Premium registries have higher limits on constraints, such as storage and concurrent operations, including enhanced storage capabilities to support high-volume scenarios. In addition to higher image throughput capacity, Premium adds features like geo-replication for managing a single registry across multiple regions, maintaining a network-close registry to each deployment.
Select the Resource Group and Location, and click on Create when ready to continue.
All tiers (SKUs) have programmatic capabilities, Azure AD (Active Directory) integration, webhooks, image management, and support Windows and Linux images. The Premium with its geo-replication allows the user to retrieve the image from the closest datacenter. This is a great option for distributed users that need to access the registry.
After the Azure Container Registry creation, we can check it in Overview. On the right side within the Essentials section, we will be able to check some key settings like Login Server, which is the name that we are going to use when using docker client, as well the location and SKU, limits and metrics.
Continue your reading on: https://foxutech.com/setup-jenkins-with-azure-container-registry/
