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

Docs: Fix character format. (#12773)

Browse source 
Co-authored-by: Javier Alfonso <PhoneixSegovia@gmail.com>
This commit is contained in:
k8s-infra-cherrypick-robot 2025-02-03 04:04:58 -08:00 committed by GitHub
parent 84f668f45e
commit 7c33e6e0c1
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/faq.md
View file

@ -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.