DevFW-CICD/ingress-nginx-helm
14
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Clarify how to disable the GCE ingress controller

Browse source
This commit is contained in:
Tony Li 2017-09-13 19:27:37 -04:00 committed by GitHub
parent 6cca4c5cdd
commit 97e924d124
1 changed files with 18 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
examples/deployment/gce/README.md
View file

@ -12,14 +12,27 @@ controller.__
As of Kubernetes 1.3, GLBC runs as a static pod on the master. If you want to As of Kubernetes 1.3, GLBC runs as a static pod on the master. If you want to
totally disable it, you can ssh into the master node and delete the GLBC totally disable it, you can ssh into the master node and delete the GLBC
manifest file found at `/etc/kubernetes/manifests/glbc.manifest`. You can also manifest file found at `/etc/kubernetes/manifests/glbc.manifest`.
disable it on GKE at cluster bring-up time through the `disable-addons` flag:
### Disabling GCE ingress on cluster creation
Disable it on GKE at cluster bring-up time through the `disable-addons` flag:
```console ```console
gcloud container clusters create mycluster --network "default" --num-nodes 1 \ gcloud container clusters create mycluster --network "default" --num-nodes 1 \
--machine-type n1-standard-2 --zone $ZONE \ --machine-type n1-standard-2 \
--disable-addons HttpLoadBalancing \ --zone $ZONE \
--disk-size 50 --scopes storage-full --disk-size 50 \
--scopes storage-full \
--disable-addons HttpLoadBalancing
```
### Disabling GCE ingress by existing cluster
Disable it on GKE for an existing cluster through the `update-addons` flag:
```console
gcloud container clusters update mycluster --update-addons HttpLoadBalancing=DISABLED
``` ```
## Deploying a new controller ## Deploying a new controller