<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=20467) </details> <!--IssueSummary end--> ### Summary (Summarize the bug encountered concisely) ### Steps to reproduce Install gitlab omnibus on dedicated server with Docker container. Enable gitlab container registry. Push container into registry. Enable ci with kubernetes executor Create secret with kubectl create secret docker-registry regsecret --docker-server=<your-registry-server> --docker-username=<your-name> --docker-password=<your-pword> --docker-email=<your-email> Add regsecret with image_pull_secrets into gitlab configmap. Try to pull image from registry with gitlab Ci ### What is the current *bug* behavior? (What actually happens) I can not pull private image from registry The message issue is : ERROR: Job failed: image pull failed: Back-off pulling image "hostname:port/group/project" ### What is the expected *correct* behavior? Pull image from registry by ci (What you should see instead) ERROR: Job failed: image pull failed: Back-off pulling image "hostname:port/group/project" #### Results of GitLab environment info <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`) </pre> </details> #### Results of GitLab application Check <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`) </pre> </details> ## Possible Workarounds Ordered by oldest to newest: 1. https://gitlab.com/gitlab-org/gitlab/-/issues/20467#note_215095464 add secret and change imagePullSecrets settings 1. https://gitlab.com/gitlab-org/gitlab/-/issues/20467#note_215095510 create deploy token 1. https://gitlab.com/gitlab-org/gitlab/-/issues/20467#note_215095525 create secret and modify auths 1. https://gitlab.com/gitlab-org/gitlab/-/issues/20467#note_215095526 add a secret that can read the private GCR repositories 1. https://gitlab.com/gitlab-org/kubernetes-gitlab-demo/-/issues/24#note_88894586 changing affinity settings 1. https://gitlab.com/gitlab-org/charts/gitlab/-/issues/1249#note_154554650 overwriting externalTrafficPolicy to be cluster