Skip to main content

Upgrade azure container registry's (ACR) SKU via azure CLI

ACR - Azure Container Registry is azure based container registry/repository to pull and push containerized images.

Tools like azure powershell, CLI are sometimes faster than azure portal to perform some operations. In this post, we are going to upgrade azure container registry's sku from standard to premium.

you people may ask me why should it get changed and let it be, I hear.

The reason behind it is, I would like to restrict ACR from all IP(s) except some selective IP(s) but Standard SKU acr is not supported this feature. so that we need to upgrade it.

you can prefer either cloudshell or local powershell, bash based on your convenient.

If you choose cloudshell, you may not need to install most of the powershell or bash related modules explicitly and need not to login explictly like az login and/or Connect-AzAccount but you need to have cloud resources like azure file share one time created for an account and incur some costs.

If you prefer local powershell, you need to install and import azure required modules and login everytime after you closed the session

please look into the below image where we upgrade/change SKU of ACR from standard to Premium via azure CLI command

Comments

Popular posts from this blog

Azure Public IP(s) are zone redundant free of cost natively - Generally Available Availability zone gives high availability to an application as well as information by forestalling the physical datacenter disappointments by involving replication of the asset in extra datacenter. Azure typically has 3 zones per region (and not all regions support zone). Thus, while setting up the environment we really want to pick the right region based on our usecase. Public IP helps to access a resource or an application publicly. Azure offers 2 types of SKU for public IP as below Basic Standard Only Standard SKU gives zone facility. Basic SKU is always non-zonal and this SKU also will be retired 09/2025. Standard public IP can be fell into any of the below category No Zone / Non-Zonal - No availability zone at all Zonal - Our services can be replicated in any one of selected zones from three zones. Zone redundant - Resource will be replicated in all 3 zones. It is opposite of...
create and read a file in Linux As a cloud and Devops engineers, we need to know to work with Linux is always helpful to handle some critical situations. There are multiple ways to create and read a file in Linux. In this article we're going to learn about touch command. Let's work with followings in this article pwd - To show present working directory touch - To create an empty file ls - To list the files from the current directory echo - To display message as well as write into a file. '>' - write into a file. '>>' - append it to a file cat - To read content of file we'll see writing and appending into a file in my upcoming post.
Avoid YAML Validation error in azure devops pipeline Hi All! Consider a scenario that you committed a YML CI/CD file on the repository with some syntax, indentation and/or other error(s). so that pipeline failed. After you find some errors and rectified in the repository file and committed again but pipeline still gets failed because some errors are still there. Now you afraid that even if you fixed error in all the places, what happens if pipeline failed again because your project lead or manager set up build notification mail trigger for build success and fails. you need to answer them for build fail reason. Azure devops pipelines offers YAML validation feature after altered and before committed and before run pipeline. To utilize this feature, what we do is, Instead of modifying the file from repository, Do as below Go to the specific build click "Edit Pipeline" Modify/fix errors and click "validate" as shown in the picture below ...