From c2bab5a2c90ae1c3edbb4e05bb98b880184be51e Mon Sep 17 00:00:00 2001 From: Javier Alfonso Date: Mon, 3 Feb 2025 13:02:57 +0100 Subject: [PATCH] Docs: Fix character format. (#12770) --- docs/faq.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index 97d3325ca..ea1e4d308 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -165,8 +165,8 @@ default on the next breaking change release, set for 2.0.0. - When "`ingress.spec.rules.http.pathType=Exact`" or "`pathType=Prefix`", this validation will limit the characters accepted on the field "`ingress.spec.rules.http.paths.path`", -to "`alphanumeric characters`", and `"/," "_," "-."` Also, in this case, -the path should start with `"/."` +to "`alphanumeric characters`", and "`/`", "`_`", "`-`". Also, in this case, +the path should start with "`/`". - When the ingress resource path contains other characters (like on rewrite configurations), the pathType value should be "`ImplementationSpecific`". @@ -175,7 +175,7 @@ configurations), the pathType value should be "`ImplementationSpecific`". - When this option is enabled, the validation will happen on the Admission Webhook. So if any new ingress object contains characters other than -alphanumeric characters, and, `"/,","_","-"`, in the `path` field, but +alphanumeric characters, and, "`/`", "`_`", "`-`", in the `path` field, but is not using `pathType` value as `ImplementationSpecific`, then the ingress object will be denied admission.