istio.io: Installation with helm fails on git master

The following works fine with istio 1.0.2, but fails on git master:

$ git clone https://github.com/istio/istio
$ cd istio
$ helm-2.11.0 init --service-account tiller --tiller-namespace istio-system
$HELM_HOME has been configured at /home/ross/.helm.

Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.

Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.
To prevent this, run `helm init` with the --tiller-tls-verify flag.
For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installation
Happy Helming!
$ helm-2.11.0 --tiller-namespace istio-system install install/kubernetes/helm/istio \
     --name istio \
     --namespace istio-system
Error: found in requirements.yaml, but missing in charts/ directory: sidecarInjectorWebhook, security, ingress, gateways, mixer, nodeagent, pilot, grafana, prometheus, servicegraph, tracing, galley, kiali, certmanager

Using GKE 1.11.7, helm 2.11.0.

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 32 (23 by maintainers)

Most upvoted comments

Adapting https://github.com/istio/istio.io/issues/2787#issuecomment-439055137, here’s how to get a working helm chart for istio-1.1.0-snapshot.3, and generally for any Istio release (the original post only worked for daily builds due to how Istio stores artifacts in GCS):

helm init --client-only
helm repo add istio.io https://storage.googleapis.com/istio-release/releases/1.1.0-snapshot.3/charts
# assuming you're running in the istio release download directory
helm dependency update install/kubernetes/helm/istio

then you can install Istio or generate yamls as usual:

helm template install/kubernetes/helm/istio --name istio --namespace istio-system \
    -f install/kubernetes/helm/istio/values-istio-multicluster-gateways.yaml

To use any other release, swap out “1.1.0-snapshot.3” with the name of the tag of the release you want. E.g. Istio 1.0.4 is: helm repo add istio.io https://storage.googleapis.com/istio-release/releases/1.0.4/charts. If you point your browser at that URL you’ll get a NoSuchKey error that’s fine, it’s working as intended.


I agree with Kuat, we need better testing of the charts. We’ve had a few releases with broken installation artifacts. (Fortunately this is still a pre-release 😃 ).

Hit this issue as well.

Can someone document what the process is for changing the helm chart and testing it locally? I can imagine we would need to modify the charts to add/remove flags and run the istio tests against them.

–set servicegraph.enabled=true

FYI: Service graph is going away. In fact, for the 1.1 snapshots, I think it did go away - I doubt that setting does anything.

Replacement would be kiali.enabled.

See: https://preliminary.istio.io/docs/tasks/telemetry/kiali/

@ZackButcher Hi, When I execute the helm dependency update install/kubernetes/helm/istio I have this error :

Error: no repository definition for ../subcharts/sidecarInjectorWebhook. Please add them via 'helm repo add'

Nonetheless, charts are built in release-1.1 as well, and they can be found at https://storage.googleapis.com/istio-prerelease/daily-build/release-1.1-latest-daily/charts

On Wed, Nov 7, 2018 at 9:14 AM Tim Swanson notifications@github.com wrote:

the repo would work for both. But, for 1.1, there’s no istio-cni in the istio/istio helm charts requirements.yaml so it shouldn’t be required for 1.1.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/istio/istio.io/issues/2787#issuecomment-436702761, or mute the thread https://github.com/notifications/unsubscribe-auth/AeRtkJC1fL-syScdKnDYQPTJz1zUk7xDks5usxTugaJpZM4XxlJl .

I fixed this by first running

helm dep update install/kubernetes/helm/istio

Which creates the following:

	install/kubernetes/helm/istio/charts/
	install/kubernetes/helm/istio/requirements.lock

After that I can do the helm install.

@sdake Do we need to commit these files to master, or is there another way to do it dynamically?