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

make more clear gce deployment docs

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

6
examples/deployment/gce/README.md
View file

@ -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 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 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 to debug or otherwise observe its operation (eg via kubectl logs).__
deploying another one in your cluster, make sure you disable the master
controller.__ __Before deploying another one in your cluster, make sure you disable the master controller.__
## Disabling the master controller ## Disabling the master controller