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

expand on soft disable

Browse source
This commit is contained in:
Tony Li 2017-09-13 21:37:12 -04:00
parent f59e4a7b4a
commit 19f49d5da0
No known key found for this signature in database
GPG key ID: E73DA11CDB50D072
1 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
docs/faq/gce.md
View file

@ -286,11 +286,12 @@ If you want to disable it, you have 3 options:
### Soft disable ### Soft disable
1. Have it no-op based on the `ingress.class` annotation as shown [here](README.md#how-do-i-disable-an-ingress-controller) 1. Have it no-op for an Ingress resource based on the `ingress.class` annotation as shown [here](README.md#how-do-i-disable-an-ingress-controller).
This can also be used to use one of the other Ingress controllers at the same time as the GCE controller.
### Hard disable ### Hard disable
2. SSH into the GCE master node and delete the GLBC manifest file found at `/etc/kubernetes/manifests/glbc.manifest` 2. SSH into the GCE master node and delete the GLBC manifest file found at `/etc/kubernetes/manifests/glbc.manifest`.
3. Disable the addon in GKE: 3. Disable the addon in GKE:
#### Disabling GCE ingress on cluster creation #### Disabling GCE ingress on cluster creation