Azure Container Registry Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
=Pulling Images to a Kubernetes Cluster= | =Pulling Images to a Kubernetes Cluster= | ||
==Pulling Images to AKS== | ==Pulling Images to AKS== | ||
===Integrate the ACR instance with the AKS Cluster=== | |||
{{External|https://docs.microsoft.com/en-us/azure/aks/cluster-container-registry-integration}} | {{External|https://docs.microsoft.com/en-us/azure/aks/cluster-container-registry-integration}} | ||
[[AKS]] can be integrated with ACR, so images stored in the ACR instances are downloaded without any individual authentication configuration at pod level. [[Kubernetes_Cluster_Configuration_Concepts#imagePullSecrets|imagePullSecrets]] become unnecessary. The integration configuration procedure implies configuring authentication between two Azure services. | [[AKS]] can be integrated with ACR, so images stored in the ACR instances are downloaded without any individual authentication configuration at pod level. [[Kubernetes_Cluster_Configuration_Concepts#imagePullSecrets|imagePullSecrets]] become unnecessary. The integration configuration procedure implies configuring authentication between two Azure services. | ||
Revision as of 01:49, 13 April 2021
Internal
Pulling Images to a Kubernetes Cluster
Pulling Images to AKS
Integrate the ACR instance with the AKS Cluster
AKS can be integrated with ACR, so images stored in the ACR instances are downloaded without any individual authentication configuration at pod level. imagePullSecrets become unnecessary. The integration configuration procedure implies configuring authentication between two Azure services.
Operational details: