From f59e4a7b4a69f1da4538cda2a4a68f42bdde2865 Mon Sep 17 00:00:00 2001 From: Tony Li Date: Wed, 13 Sep 2017 21:18:47 -0400 Subject: [PATCH] make more clear gce deployment docs --- examples/deployment/gce/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/examples/deployment/gce/README.md b/examples/deployment/gce/README.md index 68eea05e9..229478917 100644 --- a/examples/deployment/gce/README.md +++ b/examples/deployment/gce/README.md @@ -4,9 +4,9 @@ This example demonstrates the deployment of a GCE Ingress controller. Note: __all GCE/GKE clusters already have an Ingress controller running on the master. The only reason to deploy another GCE controller is if you want -to debug or otherwise observe its operation (eg via kubectl logs). Before -deploying another one in your cluster, make sure you disable the master -controller.__ +to debug or otherwise observe its operation (eg via kubectl logs).__ + +__Before deploying another one in your cluster, make sure you disable the master controller.__ ## Disabling the master controller