Greetings, I am using the Kubernetes integration with Gitlab, have a private runner and helm installed in my namespace. Using this “Internal” project, you can get an idea of what I am trying to do. Pushing image to private docker registry in CI works fine, but later, when helm attempts to pull the image, it fails with HTTP Basic: Access denied
The secret does exist, and is created with the same username and password that docker login uses before pushing the image to the registry, but when I make this project private, or clone it, it always fails when it’s private.
apiVersion: v1 data: .dockerconfigjson: [REDACTED] kind: Secret metadata: creationTimestamp: 2018-07-10T18:20:57Z name: gitlab-registry namespace: kube-test-7268306 resourceVersion: "6243465" selfLink: /api/v1/namespaces/kube-test-7268306/secrets/gitlab-registry uid: fdc1e77c-846d-11e8-9cf9-42010a960012 type: kubernetes.io/dockerconfigjson
I have seen in various posts that CI does and does not work with private repositories. I’ve also see suggestions to use GCR for a registry substitute, since the service account can be giving access to those registries, but I was kinda hoping to use the Gitlab native registry. Can anyone confirm if this works? or even if I’m going in the wrong direction?