Skip to content

Commit c2bab5a

Browse files
authored
Docs: Fix character format. (#12770)
1 parent 01d0a20 commit c2bab5a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/faq.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -165,8 +165,8 @@ default on the next breaking change release, set for 2.0.0.
165165

166166
- When "`ingress.spec.rules.http.pathType=Exact`" or "`pathType=Prefix`", this
167167
validation will limit the characters accepted on the field "`ingress.spec.rules.http.paths.path`",
168-
to "`alphanumeric characters`", and `"/," "_," "-."` Also, in this case,
169-
the path should start with `"/."`
168+
to "`alphanumeric characters`", and "`/`", "`_`", "`-`". Also, in this case,
169+
the path should start with "`/`".
170170

171171
- When the ingress resource path contains other characters (like on rewrite
172172
configurations), the pathType value should be "`ImplementationSpecific`".
@@ -175,7 +175,7 @@ configurations), the pathType value should be "`ImplementationSpecific`".
175175

176176
- When this option is enabled, the validation will happen on the Admission
177177
Webhook. So if any new ingress object contains characters other than
178-
alphanumeric characters, and, `"/,","_","-"`, in the `path` field, but
178+
alphanumeric characters, and, "`/`", "`_`", "`-`", in the `path` field, but
179179
is not using `pathType` value as `ImplementationSpecific`, then the ingress
180180
object will be denied admission.
181181

0 commit comments

Comments
 (0)