Skip to content

fix helm3 install steps #29723

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 22, 2020
Merged

fix helm3 install steps #29723

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions manifests/charts/README-helm3.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,38 +25,38 @@ helm install istio-base -n istio-system manifests/charts/base
helm install -n istio-system istio-17 manifests/charts/istio-control/istio-discovery

helm install -n istio-system istio-canary manifests/charts/istio-control/istio-discovery \
-f manifests/charts/global.yaml --set revision=canary
--set revision=canary

helm install -n istio-system istio-mytest manifests/charts/istio-control/istio-discovery \
-f manifests/charts/global.yaml --set revision=mytest
--set revision=mytest
```

- `gateways` install a load balancer with `ingress` and `egress`. You can install it multiple times with different revisions but they must be installed in separate namespaces.

Ingress secrets and access should be separated from the control plane.

```console
helm install -n istio-system istio-ingress manifests/charts/gateways/istio-ingress -f manifests/charts/global.yaml
helm install -n istio-system istio-ingress manifests/charts/gateways/istio-ingress

kubectl create ns istio-ingress-canary
helm install -n istio-ingress-canary istio-ingress-canary manifests/charts/gateways/istio-ingress \
-f manifests/charts/global.yaml --set revision=canary
--set revision=canary
```

Egress secrets and access should be separated from the control plane.

```console
helm install -n istio-system istio-egress manifests/charts/gateways/istio-egress -f manifests/charts/global.yaml
helm install -n istio-system istio-egress manifests/charts/gateways/istio-egress

kubectl create ns istio-egress-canary
helm install -n istio-egress-canary istio-egress-canary manifests/charts/gateways/istio-egress \
-f manifests/charts/global.yaml --set revision=canary
--set revision=canary
```

- 'istio-cni' installs the CNI plugin. This should be installed after the 'base' chart and prior to `istiod`. Need to add `--set istio_cni.enabled=true` to the `istiod` install to enable its usage.

```console
helm install istio-cni -n istio-system manifests/charts/istio-cni -f manifests/charts/global.yaml
helm install istio-cni -n istio-system manifests/charts/istio-cni
```

## Namespaces
Expand Down