Interactive push/pull by individual developer or tester Portal deployment of image from registry to Azure App Service or Azure Container Instances Unattended pull to AKS cluster from registry in another AD tenant Only available with AKS cluster Can't be used for cross-tenant authenticationĮnable when AKS cluster created or updated Unattended pull to AKS cluster in the same or a different subscription Use only from select Azure services that support managed identities for Azure resourcesĪttach registry when AKS cluster created or updated
Unattended push from Azure CI/CD pipeline Unattended pull to Azure services Unattended push from CI/CD pipeline Unattended pull to Azure or external servicesĭocker login az acr login in Azure CLI Connect-AzContainerRegistry in Azure PowerShell Interactive push/pull by developers, testersĭocker login az acr login in Azure CLI Connect-AzContainerRegistry in Azure PowerShell Registry login settings in APIs or tooling Kubernetes pull secret MethodĪzure role-based access control (Azure RBAC)Īz acr login in Azure CLI Connect-AzContainerRegistry in Azure PowerShell The following table lists available authentication methods and typical scenarios. If you use a container registry with Azure Kubernetes Service (AKS) or another Kubernetes cluster, see Scenarios to authenticate with Azure Container Registry from Kubernetes. Applications and container orchestrators can perform unattended, or "headless," authentication by using an Azure Active Directory (Azure AD) service principal.Authenticate to a registry directly via individual login.There are several ways to authenticate with an Azure container registry, each of which is applicable to one or more registry usage scenarios.
0 kommentar(er)
