Skip to main content

Link an Azure Container Registry to multiple AKS clusters

To link an Azure Container Registry(ACR) to an AKS cluster, you can do this during cluster creation or set it up after the cluster is up and running.

Create a new cluster with ACR:

az aks create -n myAKSCluster -g myResourceGroup --generate-ssh-keys --attach-acr myContainerRegistry

Link ACR after creation:

az aks update -n myAKSCluster -g myResourceGroup --attach-acr myContainerRegistry

This works as long as the ACR and the AKS cluster are inside the same subscription.  If you try the command above with the ACR and AKS in different subscriptions, you get the following error message:

cli.azure.cli.core.azclierror: The resource with name 'myContainerRegistry' and type 'Microsoft.ContainerRegistry/registries' could not be found in subscription 'MySubscription'.

cli.azure.cli.core.azclierror: The resource with name 'myContainerRegistry' and type 'Microsoft.ContainerRegistry/registries' could not be found in subscription 'MySubscription'.

This doesn’t mean that this is not possible. To get this working you need to specify the complete resource URI/

az aks update --subscription MySubscription -g myResourceGroup -n myAKSCluster --attach-acr "/subscriptions/f84a2db1-aede-57cd-a7c2-e55f8b68b8ef/resourceGroups/myOtherResourceGroup/providers/Microsoft.ContainerRegistry/registries/myContainerRegistry"

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more