whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update ingress-controllers.md (#14803)

Browse Source 
I think what is meant is "to provide a default ingress CONTROLLER"
This commit is contained in:
Serdar Osman Onur
2019-06-19 01:34:32 +03:00
committed by Kubernetes Prow Robot
parent b2c496aec3
commit cc4c4789ce
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/services-networking/ingress-controllers.md
+1 -1
View File
@@ -55,7 +55,7 @@ within a cluster. When you create an ingress, you should annotate each ingress w
[`ingress.class`](https://git.k8s.io/ingress-gce/docs/faq/README.md#how-do-i-run-multiple-ingress-controllers-in-the-same-cluster)
to indicate which ingress controller should be used if more than one exists within your cluster.
If you do not define a class, your cloud provider may use a default ingress provider.
If you do not define a class, your cloud provider may use a default ingress controller.
Ideally, all ingress controllers should fulfill this specification, but the various ingress
controllers operate slightly differently.