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

docs: use generic instead of OSS controller

Browse source 
This term was really confusing me because all of these controllers in
this repo are OSS. So, instead use the term generic and define it upon
first use.
This commit is contained in:
Brandon Philips 2017-04-01 17:02:54 +02:00
parent c14d0d852b
commit 8c9e88058c
2 changed files with 10 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

4
examples/PREREQUISITES.md
View file

@ -10,12 +10,12 @@ Unless you're running on a cloudprovider that supports Ingress out of the box
## Firewall rules
If you're using a bare-metal controller (eg the nginx ingress controller), you
If you're using a generic controller (eg the nginx ingress controller), you
will need to create a firewall rule that targets port 80/443 on the specific VMs
the nginx controller is running on. On cloudproviders, the respective backend
will auto-create firewall rules for your Ingress.
If you'd like to auto-create firewall rules for an OSS Ingress controller,
If you'd like to auto-create firewall rules for an Ingress controller,
you can put it behind a Service of `Type=Loadbalancer` as shown in
[this example](/examples/static-ip/nginx#acquiring-an-ip).