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

Clarify list

Browse source 
Make it clear it is not a list of steps, but a list of options.
This commit is contained in:
Tony Li 2017-09-26 14:45:25 -04:00 committed by GitHub
parent fd1b0525a1
commit 3ef5182ebc
1 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
docs/faq/gce.md
View file

@ -286,13 +286,14 @@ If you want to disable it, you have 3 options:
### Soft disable ### Soft disable
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). Option 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. 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`. Option 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:
Option 3. Disable the addon in GKE via `gcloud`:
#### Disabling GCE ingress on cluster creation #### Disabling GCE ingress on cluster creation