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?
Cheers
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?
Cheers
Hi, you can use the container-registry
flag in order to specify your private registry.
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...
No worries Regarding the credentials I would try to set the imagePullSecrets field in the spec
of the podTemplate
. It should work for any component of the stack.
Perfect! I'll try that. Many thanks for your help
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.