From 9f9122c38141542aac7efb2f09f610e4ece57605 Mon Sep 17 00:00:00 2001 From: Long Wu Yuan Date: Sun, 5 Sep 2021 23:52:28 +0530 Subject: [PATCH] fix 7591 (#7598) --- docs/index.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/index.md b/docs/index.md index 601023215..cdcd4f896 100644 --- a/docs/index.md +++ b/docs/index.md @@ -165,8 +165,5 @@ Bear in mind that, if your `Ingress-Nginx-Controller-nginx2` is started with the - and also objects pointing to the ingressClass that have the same .spec.controller as configured in `--controller-class` -## Why is the ingressClassResource disabled by default in the helm chart ? -- If this field is set to enabled value and there are existing ingress objects in the cluster, then the existing ingress objects will not be honored and only any new ingress object you create will inherit the ingressClass value. - ## I am seeing this error message in the logs of the Ingress-NGINX controller "ingress class annotation is not equal to the expected by Ingress Controller". Why ? - It is highly likely that you will also see the name of the ingress resource in the same error message. This error messsage has been observed on use the deprecated annotation, to spec the ingressClass, in a ingress resource manifest. It is recommended to use the ingress.spec.ingressClassName field, of the ingress resource, to spec the name of the ingressClass of the ingress resource being configured.