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

Fix minor typos in Ingress admin guide

Browse source
This commit is contained in:
Malepati Bala Siva Sai Akhil 2017-08-17 03:43:41 +05:30 committed by GitHub
parent 794c25b485
commit 0df6e45751
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

@ -20,7 +20,7 @@ Ingress controller behind an ELB on AWS, as shows in the [next section](#stacked
## Stacked deployments ## Stacked deployments
__Behind a LoadBalancer Service__: You can deploy an generic controller behind a __Behind a LoadBalancer Service__: You can deploy a generic controller behind a
Service of `Type=LoadBalancer`, by following this [example](/examples/static-ip/nginx#acquiring-an-ip). Service of `Type=LoadBalancer`, by following this [example](/examples/static-ip/nginx#acquiring-an-ip).
More specifically, first create a LoadBalancer Service that selects the generic More specifically, first create a LoadBalancer Service that selects the generic
controller pods, then start the generic controller with the `--publish-service` controller pods, then start the generic controller with the `--publish-service`
@ -37,7 +37,7 @@ TODO: Write an example
## Daemonset ## Daemonset
Neither a single pod or bank of generic controllers scales with the cluster size. Neither a single pod nor bank of generic controllers scale with the cluster size.
If you create a daemonset of generic Ingress controllers, every new node If you create a daemonset of generic Ingress controllers, every new node
automatically gets an instance of the controller listening on the specified automatically gets an instance of the controller listening on the specified
ports. ports.