"ImagePullBackOff" status of two pods in IFS Cloud 23.2.2

Hi PlaSandaM,

The ImagePullBackOff status means that Kubernetes could not pull a container image. It will continue to try to pull the container image with an increasing back-off delay until resolved.

The error "failed to copy: read tcp 10.0.0.149:37644->20.101.176.184:443: read: connection reset by peer" indicates that a connection from 10.0.0.149 (your IFS remote server) to 20.101.176.184 (=ifscloud.jfrog.io, where the container image exists) could not be made.

This indicates a network issue. It could be for a number of reasons, including (though not limited to): a missing route, the port (443) is being blocked by a firewall, a proxy issue etc. You will need to check with the network administrator to understand why this is failing.

Best regards -- Ben

Thank you @Ben Monroe,

I verified the connectivity and it looks like MWS server and reach the repository.

I recreate the pods and the errors I can see in the logs now are,

Failed to load logs: container "ifsapp-native-server" in pod "ifsapp-native-server-7454c96b6b-mr4zt" is waiting to start: image can't be pulled

Reason: BadRequest (400)

Failed to load logs: container "ifsapp-connect" in pod "ifsapp-connect-6dff456d54-xjz2b" is waiting to start: trying and failing to pull image

Reason: BadRequest (400)

Any further recommendations/suggestions to get this issue resolved?

Thank you.