For our deployment, we would like to not download the docker images from the internet (dockerhub) everytime.
Meaning we want to get all images for istio-init and istio and store it in our local repository. This step is required for security/certification etc.
Question 1
Now Istio-init and Istio are made up of multiple disparate pieces (meaning there are many docker images). What’s the best way to source all of these. Is there are quick way to get all these images as collection ?
Question 2
And finally this also means the helm charts would now need to point to the local repo. What’s the best way to alter the charts to point to the local repository ? I’m asking this question from future maintainability when newer versions of istio are released how can I get them installed (from local source) with NO or minimal changes to the chart ?
Hi @adurai81, would you mind listing out the steps you followed to make this work? I also need the images to be stored on and pulled from our servers per company policy.
When I did the Quick Install, I had to update the image tags in the demo yaml to point to the ones that I re-tagged and uploaded to our registry. I’d like to know how you did it with helm, for both the initial installation and later upgrades.
Thanks. It’s very similar to what I did, except that I used quick install to load all the images and I used quick install again on another box after updating the demo yaml to point to my uploaded images.
Have you tried upgrading? I’m not that familiar with Helm yet. Is it just a matter of performing the same steps with a new helm chart?
Istio core installed
✘ Istiod encountered an error: failed to wait for resource: resources not ready after 5m0s: timed out waiting for the condition
Deployment/istio-system/istiod
✘ Egress gateways encountered an error: failed to wait for resource: resources not ready after 5m0s: timed out waiting for the condition
Deployment/istio-system/istio-egressgateway
✘ Ingress gateways encountered an error: failed to wait for resource: resources not ready after 5m0s: timed out waiting for the condition
Deployment/istio-system/istio-ingressgateway
✘ Addons encountered an error: failed to wait for resource: resources not ready after 5m0s: timed out waiting for the condition
Deployment/istio-system/prometheus
Pruning removed resources Error: failed to apply manifests: errors occurred during operation
We do not use helm for the installation, we would like to know how to do the installation using istioctl tool.