Welcome to the Linux Foundation Forum!

Lab 3.3 Configure Probes - Liveness Probe - goproxy image not loading

I have followed directions to add the goproxy container with the LivenessProbe. However when I create the deployment the goproxy container is not able to start. It has STATUS ImagePullBackoff. I am able to run the simpleApp with and without its own Readiness Probe per the lab. But goproxy is not working.

$ kubectl get pod

NAME                                READY     STATUS             RESTARTS   AGE
nginx-b68dd9f75-j98b8      1/1     Running                   1          42d
registry-6b5bb79c4-5gbwc  1/1     Running                  1          42d
try1-7bfc984497-ch5xf       1/2     ImagePullBackOff     0          18m
try1-7bfc984497-nlblj         1/2     ImagePullBackOff     0          18m
try1-7bfc984497-qrxp9      1/2     ImagePullBackOff      0          18m
try1-7bfc984497-sq7zv      1/2     ImagePullBackOff      0          18m
try1-7bfc984497-tqhx6      1/2     ImagePullBackOff      0          18m
try1-7bfc984497-wxrtk      1/2     ImagePullBackOff      0          18m

$sudo podman images

REPOSITORY                           TAG      IMAGE ID      CREATED        SIZE
..etc..
k8s.gcr.io/goproxy                   0.1      ca30c529755f  6 years ago    5.5 MB

$ simpleapp.yaml excerpt
   etc..
   spec:
      containers:
      - image: 10.104.1.130:5000/simpleapp
        imagePullPolicy: Always
        name: simpleapp
        resources: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
      - name: goproxy
        image: k8s.gcr.oi/goproxy:0.1
        ports:
        - containerPort: 8080
        readinessProbe:
          tcpSocket:
            port: 8080
          initialDelaySeconds: 5
          periodSeconds: 10
        livenessProbe:
          tcpSocket:
            port: 8080
          initialDelaySeconds: 15
          periodSeconds: 20
    etc..

Thanks for any help you can give!

Kathy

Comments

  • serewicz
    serewicz Posts: 997
    edited April 5

    Hello,

    You have a typo. The image location is k8s.gcr .io not oi.

    Regards,

  • katcrave
    katcrave Posts: 4

    Oh my!! Thank you, I thought I compared it many times!

Categories

Upcoming Training