From fbcc8602b4ad4dadd1ce2656dbea3c00d9dc1f02 Mon Sep 17 00:00:00 2001 From: Anyul Rivas Date: Thu, 29 Feb 2024 10:33:55 +0100 Subject: [PATCH] Update content/es/docs/concepts/services-networking/ingress.md Co-authored-by: Victor Morales --- content/es/docs/concepts/services-networking/ingress.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/es/docs/concepts/services-networking/ingress.md b/content/es/docs/concepts/services-networking/ingress.md index 7cc08c9c8e..2cd1f0796b 100644 --- a/content/es/docs/concepts/services-networking/ingress.md +++ b/content/es/docs/concepts/services-networking/ingress.md @@ -438,7 +438,7 @@ como el predeterminado en tu clúster. Existen algunos controladores de ingress, que funcionan sin una definición de una `ingressClass`. Por ejemplo, el controlador Ingress-NGINX se puede configurar con -una [bandera](https://kubernetes.github.io/ingress-nginx/#what-is-the-flag-watch-ingress-without-class) +una [opción](https://kubernetes.github.io/ingress-nginx/#what-is-the-flag-watch-ingress-without-class) `--watch-ingress-without-class`. Sin embargo, se [recomienda](https://kubernetes.github.io/ingress-nginx/#i-have-only-one-instance-of-the-ingresss-nginx-controller-in-my-cluster-what-should-i-do)