# Authorize helm chart in docker.io

**URL:** <https://discuss.kubernetes.io/t/authorize-helm-chart-in-docker-io/16278>\
**Category:** General Discussions\
**Tags:** development\
**Created:** [June 9, 2021, 3:04pm UTC](https://discuss.kubernetes.io/t/authorize-helm-chart-in-docker-io/16278 "2021-06-09T15:04:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![soberaccounthere](https://avatars.discourse-cdn.com/v4/letter/s/eb9ed0/32.png) [@soberaccounthere](https://discuss.kubernetes.io/u/soberaccounthere)\
**Post date:** [June 9, 2021, 3:04pm UTC](https://discuss.kubernetes.io/t/authorize-helm-chart-in-docker-io/16278/1 "2021-06-09T15:04:49Z")

</div>

Hey i’m trying to authorize my pods in [docker.io](http://docker.io) because i got:

`Warning Failed 11m (x3 over 12m) kubelet Failed to pull image "busybox:latest": rpc error: code = Unknown desc = Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit`

I already have a secret set up:

```
> kubectl get secret regcred

NAME TYPE DATA AGE
regcred kubernetes.io/dockerconfigjson 1 105m

```

Unfortunately I have no idea where to “throw” it if I pull the whole from chart:

```
> helm2 upgrade --namespace gitlab --install gitlab gitlab/gitlab --timeout 600 -f gitlab-conf.yaml

```

I have gitlab-conf.yaml with the given resources, etc which are on AWS. Should I customize chart in some way? Do you have any idea?

---

<div class="post-metadata">

**Author:** ![protosam](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/protosam/32/7732_2.png) [@protosam](https://discuss.kubernetes.io/u/protosam)\
**Post date:** [June 9, 2021, 5:07pm UTC](https://discuss.kubernetes.io/t/authorize-helm-chart-in-docker-io/16278/2 "2021-06-09T17:07:00Z")

</div>

[The pod must have imagePullSecrets defined](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/#create-a-pod-that-uses-your-secret).

This requires the developer that made the chart to have provided functionality for controlling the container `image` and `imagePullSecrets` values.