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

Docs: Fix link in installation instructions. (#13192)

Browse source 
Co-authored-by: lemeurherveCB <137290663+lemeurherveCB@users.noreply.github.com>
This commit is contained in:
k8s-infra-cherrypick-robot 2025-04-12 05:40:41 -07:00 • committed by GitHub
parent 910aa56e2e
commit 5f988e0d67
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/deploy/index.md
View file

@ -434,9 +434,7 @@ By default, the controller watches Ingress objects from all namespaces. If you w
use the flag `--watch-namespace` or check the Helm chart value `controller.scope` to limit the controller to a single use the flag `--watch-namespace` or check the Helm chart value `controller.scope` to limit the controller to a single
namespace. Although the use of this flag is not popular, one important fact to note is that the secret containing the default-ssl-certificate needs to also be present in the watched namespace(s). namespace. Although the use of this flag is not popular, one important fact to note is that the secret containing the default-ssl-certificate needs to also be present in the watched namespace(s).
See also See also [“How to install multiple Ingress controllers in the same cluster”](https://kubernetes.github.io/ingress-nginx/user-guide/multiple-ingress/) for more details.
[“How to easily install multiple instances of the Ingress NGINX controller in the same cluster”](https://kubernetes.github.io/ingress-nginx/#how-to-easily-install-multiple-instances-of-the-ingress-nginx-controller-in-the-same-cluster)
for more details.
### Webhook network access ### Webhook network access