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

Update README.md

Browse source
This commit is contained in:
Lion-Wei 2017-08-21 10:51:18 +08:00 committed by GitHub
parent 6ef63438b6
commit e8f3c16178
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/faq/README.md
View file

@ -6,7 +6,7 @@ in this directory with site specific information.
Table of Contents
=================
* [How is Ingress different from a Services?](#how-is-ingress-different-from-a-service)
* [How is Ingress different from a Service?](#how-is-ingress-different-from-a-service)
* [I created an Ingress and nothing happens, what now?](#i-created-an-ingress-and-nothing-happens-what-now)
* [How do I deploy an Ingress controller?](#how-do-i-deploy-an-ingress-controller)
* [Are Ingress controllers namespaced?](#are-ingress-controllers-namespaced)
@ -46,7 +46,7 @@ controller by following [this](/examples/deployment) example.
Ingress is namespaced, this means 2 Ingress objects can have the same name in 2
namespaces, and must only point to Services in its own namespace. An admin can
deploy an Ingress controller such that it only satisfies Ingress from a given
namespace, but by default, controllers will watch the entire kubernetes cluster
namespace, but by default, controllers will watch the entire Kubernetes cluster
for unsatisfied Ingress.
## How do I disable an Ingress controller?