mirror of https://github.com/istio/istio.io.git
fix istioctl cni on gke (#5987)
`istioctl manifest apply --set profile=demo --set cni.enabled=true --set values.cni.cniBinDir=/home/kubernetes/bin` by default put the `istio-cni-node` daemonset in istio-system namespace. The cni pod fails to create.
According to the helm command here 3fc0e65d94/README.md (usage)
`istio manifest` should set cni.namespace to kube-system on gke
Signed-off-by: Yuchen Dai <silentdai@gmail.com>
This commit is contained in:
parent
c863bea599
commit
34b6bb9ea5
|
@ -121,7 +121,7 @@ The following table shows the required settings for many common Kubernetes envir
|
|||
|
||||
| Hosted Cluster Type | Required Istio CNI Setting Overrides | Required Platform Setting Overrides |
|
||||
|---------------------|--------------------------------------|-------------------------------------|
|
||||
| GKE 1.9+ (see [GKE setup](#gke-setup) below for details)| `--set values.cni.cniBinDir=/home/kubernetes/bin` | enable [network-policy](https://cloud.google.com/kubernetes-engine/docs/how-to/network-policy) |
|
||||
| GKE 1.9+ (see [GKE setup](#gke-setup) below for details)| `--set cni.components.cni.namespace=kube-system --set values.cni.cniBinDir=/home/kubernetes/bin` | enable [network-policy](https://cloud.google.com/kubernetes-engine/docs/how-to/network-policy) |
|
||||
| IKS (IBM cloud) | _(none)_ | _(none)_ |
|
||||
| EKS (AWS) | _(none)_ | _(none)_ |
|
||||
| AKS (Azure) | _(none)_ | _(none)_ |
|
||||
|
|
Loading…
Reference in New Issue