make more clear gce deployment docs
This commit is contained in:
parent
b87c5ff39d
commit
f59e4a7b4a
1 changed files with 3 additions and 3 deletions
|
@ -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
|
||||
|
||||
|
|
Loading…
Reference in a new issue