<p>I wonder how does a kubernetes operator such as the <a href="https://www.jaegertracing.io/docs/1.39/operator/" rel="nofollow noreferrer">jaeger operator</a> call other images.</p>
<p>A problem I am having with the Jaeger operator for instance, is when I set up a new instance and the operator creates the required components, it calls images for those components from quay.io. Now on my setup, I am required to pull images from our local registry.</p>
<p>How can I set up the operator to use local registry instead of quay.io?</p>

Tiriyon
<p>Based on my understanding of the question, the operator creates deployment objects for other components. However, in this case only the deployment configuration is created by the operator. It is the Kubernetes Control Plane that actually pulls the image instead of the operator pod.</p>
<p>If the image is present in a public repository, then there should not be any problem with pulling the image specified in the deployment configuration. If the image resides in a private repository, authentication details for the registry must be provided to the Kubernetes control plane. The operator must create a secret containing the authentication details of the repository and provide them in the deployment configuration. The doc explains how to do this using Kubectl, but your operator can do the same thing.</p>
<p>Link: <a href="https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/" rel="nofollow noreferrer">https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/</a></p>
