I am attempting to deploy a container image to a (linux) Kubernetes cluster. Unfortunately, the only way for the cluster to obtain the image is by using a proxy (otherwise the pod results in an
ErrImagePull failure state as it’s unable to resolve the image location).
After a little research, it looks like Kubernetes will ultimately try to use the HTTP_PROXY environment variable when pulling images, but I don’t know if setting that for the user the worker runs under would interfere with other operations. Ideally this would be something we could set that would be set when running
Is there any guidance for how we can set this up? This is also only impacting a single cluster we deploy to (other clusters that receive the same package are able to reach the image repository directly), so I feel this may be better accomplished by configuring the cluster/worker nodes, and not the actual deployment process, but I’m open to any solution that would allows us to deploy correctly.