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

removed deprecation messsage for ingressClass annotation (#9357)

Browse source 
* removed deprecation messsage for ingressClass annotation

* modified: docs/user-guide/multiple-ingress.md

* modified: docs/user-guide/multiple-ingress.md

* modified: docs/user-guide/multiple-ingress.md
This commit is contained in:
Saumya 2022-12-03 10:43:54 +05:30 committed by GitHub
parent c234d1f10b
commit 5aa49dc66d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/user-guide/multiple-ingress.md
View file

@ -2,7 +2,9 @@
By default, deploying multiple Ingress controllers (e.g., `ingress-nginx` & `gce`) will result in all controllers simultaneously racing to update Ingress status fields in confusing ways.
To fix this problem, use [IngressClasses](https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-class). The `kubernetes.io/ingress.class` annotation is deprecated from kubernetes v1.22+.
To fix this problem, use [IngressClasses](https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-class). The `kubernetes.io/ingress.class` annotation is not being preferred or suggested to use as it can be deprecated in future. Better to use the field `ingress.spec.ingressClassName`.
But, when user has deployed with `scope.enabled`, then the ingress class resource field is not used.
## Using IngressClasses