Skip to content

Commit 866a0d2

Browse files
authored
Add FailedToRetrieveImagePullSecret event description to pull-image-private-registry (#41897)
1 parent f1088bc commit 866a0d2

File tree

1 file changed

+25
-0
lines changed

1 file changed

+25
-0
lines changed

content/en/docs/tasks/configure-pod-container/pull-image-private-registry.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -210,6 +210,31 @@ kubectl apply -f my-private-reg-pod.yaml
210210
kubectl get pod private-reg
211211
```
212212

213+
{{< note >}}
214+
In case the Pod fails to start with the status `ImagePullBackOff`, view the Pod events:
215+
```shell
216+
kubectl describe pod private-reg
217+
```
218+
219+
If you then see an event with the reason set to `FailedToRetrieveImagePullSecret`,
220+
Kubernetes can't find a Secret with name (`regcred`, in this example).
221+
If you specify that a Pod needs image pull credentials, the kubelet checks that it can
222+
access that Secret before attempting to pull the image.
223+
224+
Make sure that the Secret you have specified exists, and that its name is spelled properly.
225+
```shell
226+
Events:
227+
... Reason ... Message
228+
------ -------
229+
... FailedToRetrieveImagePullSecret ... Unable to retrieve some image pull secrets (<regcred>); attempting to pull the image may not succeed.
230+
```
231+
232+
233+
{{< /note >}}
234+
235+
236+
237+
213238
## {{% heading "whatsnext" %}}
214239

215240
* Learn more about [Secrets](/docs/concepts/configuration/secret/)

0 commit comments

Comments
 (0)