Bug in lab when creating pods

Service Mesh with Istio
#1

Hello,
In each lab of ICA course, when creating a test pod in the test namespace i got this error :

root@controlplane ~ ➜  kubectl get pods -n test 
NAME   READY   STATUS             RESTARTS   AGE
test   1/2     ImagePullBackOff   0          4m45s

root@controlplane ~ ✖ k describe pod test -n test 
Name:             test
Namespace:        test
Priority:         0
Service Account:  default
Node:             controlplane/192.168.121.146
Start Time:       Sat, 31 May 2025 13:05:06 +0000
Labels:           run=test
                  security.istio.io/tlsMode=istio
                  service.istio.io/canonical-name=test
                  service.istio.io/canonical-revision=latest
Annotations:      istio.io/rev: default
                  kubectl.kubernetes.io/default-container: test
                  kubectl.kubernetes.io/default-logs-container: test
                  prometheus.io/path: /stats/prometheus
                  prometheus.io/port: 15020
                  prometheus.io/scrape: true
                  sidecar.istio.io/status:
                    {"initContainers":["istio-init"],"containers":["istio-proxy"],"volumes":["workload-socket","credential-socket","workload-certs","istio-env...
Status:           Pending
IP:               10.50.0.9

…..
….
Events:
  Type     Reason     Age                    From               Message
  ----     ------     ----                   ----               -------
  Normal   Scheduled  5m23s                  default-scheduler  Successfully assigned test/test to controlplane
  Normal   Pulled     5m23s                  kubelet            Container image "docker.io/istio/proxyv2:1.18.2" already present on machine
  Normal   Created    5m23s                  kubelet            Created container istio-init
  Normal   Started    5m23s                  kubelet            Started container istio-init
  Normal   Started    5m21s                  kubelet            Started container istio-proxy
  Warning  Failed     5m21s                  kubelet            Failed to pull image "nginx": failed to pull and unpack image "docker.io/library/nginx:latest": failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/nginx/manifests/sha256:ccbbc30b4057f9364bf31e27e25c773f5f83cb3ed908bb2994cd2993fcbbad85: 429 Too Many Requests - Server message: toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit
  Normal   Pulled     5m21s                  kubelet            Container image "docker.io/istio/proxyv2:1.18.2" already present on machine
  Normal   Created    5m21s                  kubelet            Created container istio-proxy
  Normal   Pulling    4m36s (x3 over 5m22s)  kubelet            Pulling image "nginx"
  Warning  Failed     4m35s (x3 over 5m21s)  kubelet            Error: ErrImagePull
  Warning  Failed     4m35s (x2 over 5m2s)   kubelet            Failed to pull image "nginx": failed to pull and unpack image "docker.io/library/nginx:latest": failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/library/nginx/manifests/sha256:fb39280b7b9eba5727c884a3c7810002e69e8f961cc373b89c92f14961d903a0: 429 Too Many Requests - Server message: toomanyrequests: You have reached your unauthenticated pull rate limit. https://www.docker.com/increase-rate-limit
  Warning  Failed     4m23s (x5 over 5m20s)  kubelet            Error: ImagePullBackOff
  Normal   BackOff    21s (x22 over 5m20s)   kubelet            Back-off pulling image "nginx"

Should i do something ? or should i log to my personal account of docker ?

Thank is advance to this community

Greetings .

#2

Hi @houariabdelmouhssine

Are you facing this in any specific lab?

#3

Hello I’am facing this in the ICA course’s LAB , pratically in each LAB’s Section ( i’m in the traffic management LAB)

I dont know what should i do ? i cant create a test pod to verify the connection into the default ns

#4

Thanks for highlighting this. I verified and see the same behavior.

I’ll inform the lab team to look into this and fix it.

#5

Hi @houariabdelmouhssine

The issue is fixed now.

Thanks for your patience and support.

1 Like
#6

Thank you , i confirm.