From cc4c4789ceae4bb01d3cd1114761e4f022986b50 Mon Sep 17 00:00:00 2001 From: Serdar Osman Onur Date: Wed, 19 Jun 2019 01:34:32 +0300 Subject: [PATCH] Update ingress-controllers.md (#14803) I think what is meant is "to provide a default ingress CONTROLLER" --- .../en/docs/concepts/services-networking/ingress-controllers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/services-networking/ingress-controllers.md b/content/en/docs/concepts/services-networking/ingress-controllers.md index 57af46a01a..98e5bd7445 100644 --- a/content/en/docs/concepts/services-networking/ingress-controllers.md +++ b/content/en/docs/concepts/services-networking/ingress-controllers.md @@ -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.