Skip to content

Commit aadf994

Browse files
authored
minor change
1 parent c61c09e commit aadf994

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

support/azure/azure-kubernetes/extensions/cannot-pull-image-from-acr-to-aks-cluster.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Can't pull images from Azure Container Registry to Kubernetes
33
description: This article helps you troubleshoot the most common errors that you may encounter when pulling images from a container registry to an AKS cluster.
4-
ms.date: 06/04/2025
4+
ms.date: 06/05/2025
55
author: genlin
66
ms.author: genli
77
ms.reviewer: chiragpa, andbar, albarqaw, v-weizhu, v-leedennis
@@ -357,7 +357,7 @@ When multiple jobs pull the same images, the Kubelet default pull rate limit mig
357357
358358
For more information about the limit, see the [registryPullQPS configuration](https://kubernetes.io/docs/reference/config-api/kubelet-config.v1beta1/#kubelet-config-k8s-io-v1beta1-KubeletConfiguration).
359359

360-
### Solution: Change imagePullPolicy to IfNotPresent
360+
### Solution: Change the value of imagePullPolicy to IfNotPresent
361361

362362
To resolve this issue, change the value of [imagePullPolicy](https://kubernetes.io/docs/concepts/containers/images/#image-pull-policy) from `Always` to `IfNotPresent` in the deployment YAML file to prevent unnecessary pulls. `IfNotPresent` ensures that the image is pulled from the registry only if it's not already present on the node.
363363

0 commit comments

Comments
 (0)