Helm and private registrys

#1

Right now we’re deploying istio into an environment with no internet access.
For the images we’ve just mirrored istio into a private registry. For the deployment we have helm write to a file and manually update each image to point and our own registry. Finally this is pushed in with kubectl.

This works but it is a bit clunky. Just wondering if I’m missing anything or if it’s possible to support a private registry? I don’t see any options at https://istio.io/docs/reference/config/installation-options/

#2

I think the only change that you need to have within the helm chart is to update values file to point to your private registry:

global:
 # Default hub for Istio images.
 # Releases are published to docker hub under 'istio' project.
 # Daily builds from prow are on gcr.io, and nightly builds from circle on docker.io/istionightly
 hub: my-company-private/istio

And then run the install:

helm install -f values.yaml $ISTIO_HOME/install/kubernetes/helm/istio --name istio --namespace $ISTIO_NAMESPACE

1 Like
#3

Agreed with rafik8, that is exactly why we exposed the hub param in global in the first place.

#4

Ahh, ok, I missed that. And i see there are values for the images coming from quay.io as well, perfect.

Thanks for the help guys.

1 Like
closed #5
opened #6
#7

Just FYI

This solution is not completely working: