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

Merge pull request #543 from philips/use-generic-instead-of-oss

Browse source 
docs: use generic instead of OSS controller
This commit is contained in:
Manuel Alejandro de Brito Fontes 2017-04-05 13:35:22 -03:00 • committed by GitHub
commit f4a376aa83
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).