API Connect

API Connect

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Back to discussions
Expand all | Collapse all

API Connect (10.0.7.0) Operator Deployment: pod is in Init:ImagePullBackOff status

  • 1.  API Connect (10.0.7.0) Operator Deployment: pod is in Init:ImagePullBackOff status

    Posted Mon January 01, 2024 08:29 PM

    Hello,

    The API Connect (10.0.7.0) operator was deployed to a single node Kubernetes with local docker registry using SSL but self-signed cert. --tls-verify=false was used in the upload  command "docker run --rm apiconnect-image-tool-<version> upload <registry-url>". The operator was deployed with

    kubectl apply -f ibm-apiconnect-crds.yaml

    kubectl apply -f ibm-apiconnect.yaml

    kubectl apply -f ibm-datapower.yaml -n <namespace>

    The ibm-apiconnect pod is now in the state "Init:ImagePullBackOff"

    NAME                                                     READY   STATUS                  RESTARTS   AGE
    datapower-operator-5fd8bd4f8d-prr9n                      1/1     Running                 0          21m
    datapower-operator-conversion-webhook-75dd9d58f4-grxj2   1/1     Running                 0          20m
    ibm-apiconnect-779bc7cd69-c4n7k                          0/1     Init:ImagePullBackOff   0          21m

    The pod description shows the following.

    Is the issue caused by "tls: failed to verify certificate: x509: certificate signed by unknown authority"?

    Events:
      Type     Reason     Age                From               Message
      ----     ------     ----               ----               -------
      Normal   Scheduled  39s                default-scheduler  Successfully assigned apiconnect/ibm-apiconnect-779bc7cd69-c4n7k to myapi
      Normal   Pulling    26s (x2 over 40s)  kubelet            Pulling image "myapi.demo.com:5000/ibm-apiconnect-operator-init@sha256:4d0fe0398a936b3d2b00d59cc7b0fa863c9f029da096f1b4f94b011d5b8e68cc"
      Warning  Failed     26s (x2 over 40s)  kubelet            Failed to pull image "myapi.demo.com:5000/ibm-apiconnect-operator-init@sha256:4d0fe0398a936b3d2b00d59cc7b0fa863c9f029da096f1b4f94b011d5b8e68cc": failed to pull and unpack image "myapi.demo.com:5000/ibm-apiconnect-operator-init@sha256:4d0fe0398a936b3d2b00d59cc7b0fa863c9f029da096f1b4f94b011d5b8e68cc": failed to resolve reference "myapi.demo.com:5000/ibm-apiconnect-operator-init@sha256:4d0fe0398a936b3d2b00d59cc7b0fa863c9f029da096f1b4f94b011d5b8e68cc": failed to do request: Head "https://myapi.demo.com:5000/v2/ibm-apiconnect-operator-init/manifests/sha256:4d0fe0398a936b3d2b00d59cc7b0fa863c9f029da096f1b4f94b011d5b8e68cc": tls: failed to verify certificate: x509: certificate signed by unknown authority
      Warning  Failed     26s (x2 over 40s)  kubelet            Error: ErrImagePull
      Normal   BackOff    12s (x3 over 40s)  kubelet            Back-off pulling image "myapi.demo.com:5000/ibm-apiconnect-operator-init@sha256:4d0fe0398a936b3d2b00d59cc7b0fa863c9f029da096f1b4f94b011d5b8e68cc"
      Warning  Failed     12s (x3 over 40s)  kubelet            Error: ImagePullBackOff



    ------------------------------
    Frank Ning
    Technical consultant - solution architect
    Toronto ON
    ------------------------------


  • 2.  RE: API Connect (10.0.7.0) Operator Deployment: pod is in Init:ImagePullBackOff status

    Posted Tue January 02, 2024 10:12 AM

    Hello, 

    I am not able to delete the question. The issue is resolved by making SSL on the system trust the self-signed certificate.



    ------------------------------
    Frank Ning
    Technical consultant - solution architect
    Toronto ON
    ------------------------------

    Original Message


Related Content