I have similiar problem each time i create gitlab registry secrets via kubectl create secret. It just wont pull any image, but when i use this script everything works:

#!/bin/bash
#
# Create Docker Image Registry secret in Kubernetes
#
# Usage:
#   REGISTRY=registry.gitlab.com \
#   LOGIN=<your-username> \
#   PASSWORD=<your-pword> \
#   NAMESPACE=<your namespace> \
#   NAME=<secret-name> \
#   ./registry.sh
#
# The same as:
#
# kubectl create \
#         --namespace=<your-namespace> \
#         secret docker-registry <secret-name> \
#         --docker-server=<your-registry-server> \
#         --docker-username=<your-username> \
#         --docker-password=<your-pword> \

set -eo pipefail


if [ "$1" == "delete" ]; then
  kubectl delete secret \
    --namespace="${NAMESPACE}" \
    "${NAME}" || true
fi

AUTH=$(echo -n ${LOGIN}:${PASSWORD} | base64 -w 0)

export TOKEN=$(envsubst <<<'
{
   "auths":{
      "${REGISTRY}":{
         "username":"${LOGIN}",
         "password":"${PASSWORD}",
         "auth":"${AUTH}"
      }
   }
}
' | base64 -w 0)

envsubst <<<'
apiVersion: v1
kind: Secret
metadata:
  name: ${NAME}
  namespace: ${NAMESPACE}
data:
  .dockerconfigjson: ${TOKEN}
type: kubernetes.io/dockerconfigjson
' | kubectl create -f -

You need to create a secret to authorize kubernetes to pull images from the registry.

In order to do that you may need to create a Secret Object with the base64 of your local dockerconfig.json like so:

apiVersion: v1
kind: Secret
metadata:
  name: docker-registry-configuration
  namespace: your-namespace
data:
  .dockerconfigjson: base64encodedstring
type: kubernetes.io/dockerconfigjson

---


apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: your-application
  namespace: your-namespace
spec:
  template:
    spec:
      containers:
        image: myprivate.registry.com/image-name
        name: container-name
      imagePullSecrets:
      - name: docker-registry-configuration
      restartPolicy: Always
status: {}

Any movement or insight on this?

I had the same issue but in my case was a typo on the secret namespace. When I fixed that my problem got solved.