From 736d2a4ba94abcdc37e73e2d8446179b89c8dbb1 Mon Sep 17 00:00:00 2001 From: Lion-Wei Date: Fri, 18 Aug 2017 10:27:38 +0800 Subject: [PATCH] Update admin.md --- docs/admin.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/admin.md b/docs/admin.md index 61458575a..c40247bd9 100644 --- a/docs/admin.md +++ b/docs/admin.md @@ -1,4 +1,4 @@ -# Ingress admin guide +# Ingress Admin Guide 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 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). Please note that you must specify the `ingress.class` [annotation](/examples/PREREQUISITES.md#ingress-class) if you're running on a