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

fix 7591 (#7598)

Browse source
This commit is contained in:
Long Wu Yuan 2021-09-05 23:52:28 +05:30 committed by GitHub
parent 90c065d508
commit 9f9122c381
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
docs/index.md
View file

@ -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.