From 19f49d5da0ad001fc2c181866d984cf71e8e94f4 Mon Sep 17 00:00:00 2001 From: Tony Li Date: Wed, 13 Sep 2017 21:37:12 -0400 Subject: [PATCH] expand on soft disable --- docs/faq/gce.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/faq/gce.md b/docs/faq/gce.md index 5ee2902e2..85a40fe84 100644 --- a/docs/faq/gce.md +++ b/docs/faq/gce.md @@ -286,11 +286,12 @@ If you want to disable it, you have 3 options: ### 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 -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: #### Disabling GCE ingress on cluster creation