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

Deploy GitHub Pages

Browse source
This commit is contained in:
k8s-ci-robot 2020-08-21 11:38:55 +00:00
parent cb4866883e
commit 7c7ef67728
5 changed files with 52 additions and 51 deletions
Download patch file Download diff file Expand all files Collapse all files

1
user-guide/multiple-ingress/index.html
View file

@ -1224,6 +1224,7 @@ Here is a partial example:</p>
result in both or all controllers fighting to satisfy the Ingress, and all of them racing to update Ingress status field in confusing ways.</p>
<p>When running multiple ingress-nginx controllers, it will only process an unset class annotation if one of the controllers uses the default
<code>--ingress-class</code> value (see <code>IsValid</code> method in <code>internal/ingress/annotations/class/main.go</code>), otherwise the class annotation become required.</p>
<p>If <code>--ingress-class</code> is set to the default value of <code>nginx</code>, the controller will monitor Ingresses with no class annotation <em>and</em> Ingresses with annotation class set to <code>nginx</code>. Use a non-default value for <code>--ingress-class</code>, to ensure that the controller only satisfied the specific class of Ingresses.</p>
</div>