# Deploy ECK using private docker registry

**URL:** <https://discuss.elastic.co/t/deploy-eck-using-private-docker-registry/234246>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [May 26, 2020, 6:12am UTC](https://discuss.elastic.co/t/deploy-eck-using-private-docker-registry/234246 "2020-05-26T06:12:22Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kodo65](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kodo65/32/1185_2.png) [@kodo65](https://discuss.elastic.co/u/kodo65)\
**Post date:** [May 26, 2020, 6:12am UTC](https://discuss.elastic.co/t/deploy-eck-using-private-docker-registry/234246/1 "2020-05-26T06:12:22Z")

</div>

Hi!

We rely on a software supply chain in order to gain access to external components. My question is what I need to do in order to prepare ECK to pull the necessary image(s) from our private registry instead of [docker.elastic.co](http://docker.elastic.co)?

Cheers

---

<div class="post-metadata">

**Author:** ![michael.morello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.morello/32/47448_2.png) [@michael.morello](https://discuss.elastic.co/u/michael.morello)\
**Post date:** [May 26, 2020, 6:29am UTC](https://discuss.elastic.co/t/deploy-eck-using-private-docker-registry/234246/2 "2020-05-26T06:29:43Z")

</div>

Hi, you can use the [`container-registry` flag](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-operator-config.html#k8s-operator-config) in order to specify your private registry.

---

<div class="post-metadata">

**Author:** ![kodo65](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kodo65/32/1185_2.png) [@kodo65](https://discuss.elastic.co/u/kodo65)\
**Post date:** [May 26, 2020, 6:52am UTC](https://discuss.elastic.co/t/deploy-eck-using-private-docker-registry/234246/3 "2020-05-26T06:52:09Z")

</div>

Ah, perfect - I overlooked that setting 🙂 Will eck "honor" the docker pull credentials (k8s secrets) if they're present in the k8s cluster? If not, is it possible to specify them in anyway? I didn't see any related settings...

---

<div class="post-metadata">

**Author:** ![michael.morello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.morello/32/47448_2.png) [@michael.morello](https://discuss.elastic.co/u/michael.morello)\
**Post date:** [May 26, 2020, 7:16am UTC](https://discuss.elastic.co/t/deploy-eck-using-private-docker-registry/234246/4 "2020-05-26T07:16:07Z")

</div>

No worries 🙂 Regarding the credentials I would try to set the [imagePullSecrets field](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/#create-a-pod-that-uses-your-secret) in the [`spec` of the `podTemplate`](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-customize-pods.html). It should work for any component of the stack.

---

<div class="post-metadata">

**Author:** ![kodo65](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kodo65/32/1185_2.png) [@kodo65](https://discuss.elastic.co/u/kodo65)\
**Post date:** [May 26, 2020, 7:18am UTC](https://discuss.elastic.co/t/deploy-eck-using-private-docker-registry/234246/5 "2020-05-26T07:18:28Z")

</div>

Perfect! I'll try that. Many thanks for your help 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 4, 2022, 7:59am UTC](https://discuss.elastic.co/t/deploy-eck-using-private-docker-registry/234246/6 "2022-11-04T07:59:44Z")

</div>