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

Update admin.md

Browse source
This commit is contained in:
Lion-Wei 2017-08-18 10:27:38 +08:00 committed by GitHub
parent fe33cd3e46
commit 736d2a4ba9
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/admin.md
View file

@ -1,4 +1,4 @@
# Ingress admin guide # Ingress Admin Guide
This is a guide to the different deployment styles of an Ingress controller. This is a guide to the different deployment styles of an Ingress controller.
@ -8,7 +8,7 @@ __GCP__: On GCE/GKE, the Ingress controller runs on the
master. If you wish to stop this controller and run another instance on your master. If you wish to stop this controller and run another instance on your
nodes instead, you can do so by following this [example](/examples/deployment/gce). nodes instead, you can do so by following this [example](/examples/deployment/gce).
__generic__: You can deploy a generic (nginx or haproxy) Ingress controller by simply __Generic__: You can deploy a generic (nginx or haproxy) Ingress controller by simply
running it as a pod in your cluster, as shown in the [examples](/examples/deployment). running it as a pod in your cluster, as shown in the [examples](/examples/deployment).
Please note that you must specify the `ingress.class` Please note that you must specify the `ingress.class`
[annotation](/examples/PREREQUISITES.md#ingress-class) if you're running on a [annotation](/examples/PREREQUISITES.md#ingress-class) if you're running on a